QA engineers can use Selenium variables functionality to store constants, values passed to test programs from the command-line, from another program or from a file.
The plain store command is the most basic of the many store commands and can be used to simply store a constant value in a selenium variable. It takes two parameters, the text value to be stored and a selenium variable. Use the standard variable naming conventions of only alphanumeric characters when choosing a name for your variable.
Selenium commands are also called selense, which are the set of commands that run your tests. In a test script, these commands are executed in a sequence.
Selenium provides a rich set of commands for fully testing your web application according to your test cases.
By using Selenium commands (selense), QA engineers can test the existence of UI elements based on their HTML tags, test for specific content, test for broken links, input fields, selection list options, submitting forms, table data among other elements, windows size, mouse positions, alerts, Ajax functionality, pop up windows, event handling, and many other mouse-application features.
In general, Selenium commands come in three types: Actions, Accessors, and Assertions.
The Base URL field at the top of the Selenium IDE window is very useful for allowing test cases to be run across different domains. Suppose that a site named http://www.seleniummaster.com had a dev site named http://dev.seleniummaster.com Any test cases for these sites that begin with an open statement should specify a relative URL as the argument to open rather than an absolute URL (one starting with a protocol such as http: or https:).
Selenium IDE will then create an absolute URL by appending the open command’s argument onto the end of the value of Base URL. For example, the test case below would be run against http://www.seleniummaster.com/about.html.