Selenium IDE Commands

Features of Selenium Integrated Development Environment, Element Locators, Selenese Commands, Record Selenium Test Scripts or Create Test Scrips Manually, Enhance Selenium Test Cases, and Run Selenium IDE Test Suites.
Post Reply
Posts: 87
Joined: Fri Nov 23, 2018 5:29 am

Selenium IDE Commands

Post by manoj » Wed Dec 05, 2018 4:58 am

What are the Selenium IDE Commands ?

Posts: 89
Joined: Fri Nov 23, 2018 2:55 am

Re: Selenium IDE Commands

Post by ramya » Wed Dec 05, 2018 5:00 am

Each Selenium IDE test step can chiefly be split into the following three components:


Types of Selenium IDE commands

There are three flavors of Selenium IDE commands. Each of the test steps in Selenium IDE falls under any of the following categories.



Actions are those commands which interact directly with the application by either altering its state or by pouring some test data.

For Example, “type” command lets the user interact directly with the web elements like a text box. It allows them to enter a specific value in the text box and as when the value is entered; it is showed on the UI as well.

Another example is the “click” command. The “click” command lets the user manipulate with the state of the application.

In case of failure of an action type command, the test script execution halts and rest of the test steps would not be executed.


Accessors are those commands which allow the user to store certain values to a user-defined variable. These stored values can be later on used to create assertions and verifications.

For example, “storeAllLinks” reads and stores all the hyperlinks available within a web page into a user-defined variable. Remember the variable is of array type if there are multiple values to store.


Assertions are very similar to Accessors as they do not interact with the application directly. Assertions are used to verify the current state of the application with an expected state.

Forms of Assertions:

#1. assert – the “assert” command makes sure that the test execution is terminated in case of failure.

#2. verify – the “verify” command lets the Selenium IDE carry on with the test script execution even if the verification is failed.

#3. wait for – the “waitFor” command waits for a certain condition to be met before executing the next test step. The conditions are like the page to be loaded, element to be present. It allows the test execution to proceed even if the condition is not met within the stipulated waiting period.

Post Reply

Return to “Selenium IDE”