Main features of Selenium IDE are:
The main benefits of Selenium IDE are its capability to automatically record test cases, asserts and verification of UI elements in testing, multiple options for running test cases, robust set of commands, and breakpoints feature. Here are more details:
Automated Test Cases Recording
Selenium IDE can automatically record test cases using the interactions with a website as the basis; a feature which can be disabled. As the IDE records a test case, it automatically inserts commands depending on the performed actions by test developer, like entering values, clicking radio buttons, a selection from drop-down list boxes, etc.
“Assert” or “Verify” UI Elements
Selenium IDE provides developers with two modes of assertion commands which they can apply to page or UI elements: “assert” and “verify”. The difference between the two is that “verify” command will still allow a test to continue even if a failure occurs while “assert” will return an error on failure and then immediately abort test case.
Flexible Execution of Test Cases
Developers are provided with various options when running test cases. They can run test cases within the currently loaded collection of test cases or pause and then resume a test case. They are also able to enable the IDE to start with the running of the test case from specific command mid-test case or likewise, stop it from running using a specific command. Moreover, the system authorizes the running of a single command, very handy if developers are unsure if the created command is correct.
Selenium IDE has commands, called selenese, that define what IDE needs to do and are significant in virtual testing of web apps. Three types of commands are available: Accessors, Actions, and Assertions. Accessors are utilized for assessment of state application with which the results returned are kept in variables. Actions are the command for manipulating the state of a particular application such as selecting an option or clicking a link. And finally, Assertions are being called in order to verify whether or not the state of the application is similar to what is expected.
Developers are given the option to set breakpoints when developing test cases, which supports the tool’s ability to stop or start the test on a particular command. Thus, test cases can keep running until they hit a specific command in the middle of the process and then developers proceed to check errors that occurred up to that point.
The following Selenium IDE integrations are currently offered by the vendor:
Selenium IDE pricing is available in the following plans: