Agile software development is everywhere. Organisations and teams have started adopting ‘agile’
development practices to allow flexible requirement and encourage more cooperation between
programmers and customers. This leads to increased customer satisfaction as well as more rapid
release of functional software.
The agile development practice requires ‘Agile Testing’. Agile testing involves:
• Testing as early as possible and as quickly as possible
• Testing from the customer/business perspective.
• Testing often as the working software is delivered at the end of every iteration.
This demands a lot of effort from the testers. The situation often gets worse as the testing time is
not accounted properly in the iteration and also due to the delayed delivery of the software testers
have to work harder to get on top of the iterations. This leads to Testing team always lagging
behind in the iteration and always developing a backlog of stories/bugs to test.
One of the ways to address this issue in Agile testing is to have as much automation as possible.
Using of open source tools such as selenium would help a lot in Agile testing.
But even selenium could not work wonders by itself unless there is a proper approach to Agile
testing and automation by the Project.
This workshop will address the two issues highlighted above. It will first list and raise all the
issues generally faced by the testing team in Agile Environment and then would suggest ways to
organise the Agile testing. This workshop will also familiarise the users with the best practices to
be used in ‘Selenium’ automation. These best practices would help them to automate stories
quickly and effectively and at the same time allow the automation framework to be flexible
enough to respond to the frequent changes in the software which are part of agile development.
Thus the testing team will always be on top of the iterations rather than lagging behind and