|
| SeleniumWiki |
| Visit this group |
Test Driven Development uses the “test first” approach in which test cases and the unit tests are written before code is written. The unit tests are written by the developers and once the unit tests pass the developers start developing the application and code the application. The software development becomes a series of very short iterations in which test cases drive the creation of software and ultimately the design of the program. The unit tests forms the pillar for the development of the application in a TDD Development Environment.
Test automation is usually lagging behind development of new functionality. The tools that are used to automate are dependent on the UI and this causes automation of the functionality to start only after the environment and the UI are stable.
The question is should there be a separate product backlog item (PBI)/ User story for test automation in each sprint.
Automation is an integral part of a scrum development environment. Selenium is an automation tool that can be used to test the functionality in a web based project.
In the implementation of the Keyword Framework Approach for testing a web application we can used Selenium IDE as the Record/Replay tool. Once you have the script you can then run the scripts using Selenium RC or Selenium Grid.
A typical script for automation involves a number of actions or steps on a web page. I this example we will look at automation of Google’s Gmail Login page.
Here are some of the steps
1. Open http://www.gmail.com
2. Enter “user id”
3. Enter “password”
4. Click on “login button”
Here are some key reasons why we need to automate software testing:
Reusing the test scripts: When you want to execute the regression test scripts after every build it makes more sense to automate them. In case of testing web based application there is a more need to automate as the test suite has to be run on verious browsers like Internet Explorer, Firefox and other browsers.
It saves time: Running unattended automated test scripts saves human time as well as machine time than executing scripts manually
Better use of resource: While automated scripts are running unattended on machines, testers can do more useful tasks
Cost Saving: On test engagements requiring a lot of regression testing, usage of automated testing reduces the people count and time requirement to complete the engagement and helps reduce the costs
