|
Testing Web Application With Selenium IDE |

Selenium is a web applications test tool that runs within the browser.
It simulates browser interactions with web applications just as a user
would. Selenium IDE is an integrated environment that makes it easy to
write selenium tests. Selenium IDE comes as a Firefox (browser) plugin
that allows you to create, debug, edit and record tests. With selenium
IDE, you have everything you need to start writing web tests.
Selenium provides the following detailed features:
- Record and playback: Recording is the process of capturing the progress on the screen. Recorded progress can be played back as a process of running the test. By default when the selenium IDE starts, record is turned on by default. Navigating using the web browser with recording turns on captures all of the events generated by the user to the browser as tests that can then be rerun following the same recorded path.
- Field Selection with Xpath, ID or name: To be able to fill and interact with items on the browser, Selenium depends on establishing the identity of the element. Usually form elements have names and id’s and each element in the dom has an Xpath identifier. When locating items in the dom, selenium first uses the identifier as an id then as a name. If neither is available, selenium uses the Xpath locator which can be taxing especially when using the Internet Explorer web browser.
- Auto Complete for Selenium test commands: When setting up tests, selenium provided a mechanism to automatically complete commands being typed. Auto complete allows testers to quickly write test scripts or edit existing ones. This is a standard feature in any fully featured IDE.
- Walk through the tests: When tests are complete, selenium provided a mechanism to allow for walk through of the tests. This process executes all the tests in a step by step fashion as identified in the script. When running in walk through troubleshooting of the tests can be performed.
- Debug and test break points: Debugging allows testers to interrogate the IDE with the intent of fixing problems in the test scripts. A feature of debugging that is very powerful is the ability to set break points in the test scripts. When the test script is executing, it will pause at any breakpoint in the script where testers can then interact with all the variables within scope at that point.
- Save HTML tests in java, ruby or any other language: Selenium IDE creates tests in HTML. However to allow for robustness, this tests can be converted to more standard languages such as ruby or java where more programmatic control is available. Test converted to other languages cannot be reverted back to their HTML form. Look at this as a vein that does not provide mechanisms to go back to the original source.
- Auto asset of page titles: Besides creating and executing your tests, when running tests, Selenium can automatically add assert commands to verify the page titles of the pages under test. This is an extremely convenient feature that provides the first level check to validate that the page being loaded does contain the correct information to be tested.
Selenium IDE is among a suite of testing tools from ThoughtWorks under the umbrella name of Selenium. As alluded to earlier, tests can be converted no native languages such as java and ruby. In this format, tests can be run using the Selenium Remote Control (Selenium RC) that provides a rich set of features over the standard IDE including but not limited to ease of automation of the test execution process.
Selenium is a mercury poisoning treatment and for those familiar with the mercury company suite of products, the joke stems from the treatment provided by selenium to the testing process for organizations. Selenium provides features to allow for easy testing of web applications and even web pages. This ensures that developers are able to verify that the product they are developing is the right product for their customers. Besides testing, selenium can be used in the refactoring process of software development. This allows them to verify that any refactorings made in code do not interfere with the functionality of the application before it is released. Another use has been in the error reproduction process. To be able to identify and fix errors in programs, it is important for one to be able to reproduce it. Recording the reproduction process and playing it back allows developers to easily identify and resolve these problems.
Add as favourites (113) | Quote this article on your site
|
- Please keep the topic of messages relevant to the subject of the article.
- Personal verbal attacks will be deleted.
- Please don't use comments to plug your web site. Such material will be removed.
- Just ensure to *Refresh* your browser for a new security code to be displayed prior to clicking on the 'Send' button.
- Keep in mind that the above process only applies if you simply entered the wrong security code.
| |