Test Automation In An Agile Environment
Agile Teams Have Often Struggled With Getting Traditional Software Test Automation Tools... But They Need Struggle No More.
Although more and more organisations are moving towards agile software delivery, agile methodologies bring its own set of challenges. Not least functional test automation.
The truth of the matter is that traditional test tools struggle to work in an agile environment. This is mainly due to the fact that they were designed to work in a 'test last' environment whereas the agile model is more a 'test first, test continuously' model.
Traditional, heavyweight, record-and-playback tools force test teams to wait until after the software is complete (or at least the interface) before test automation can begin. After all, it's difficult to record scripts against an interface that doesn't yet exist.
As a result, these kind of tools only really suit application testing that involves long development times and strict change management regulations. Otherwise they simply wont work.
Addressing the challenges of test automation in an agile environment
Typically, software testers working with these tools have specialist skills and the cost of licenses for these products is huge so many organisations frequently choose to buy licenses for just a select few. This goes against the ethos of tight communications and close-knit working groups that are necessary in a successful agile software testing environment.
Finding the right software automation tool is therefore incredibly important as QA teams push to have a releasable version of the software from each iteration.
Furthermore, the number of tests increase exponentially with each story to the point where, if the tests were done 100% manually, the testing could actually exceed the length of the total iteration. It then becomes imperative that an option is available to reduce the time taken for manual testing.
Introducing Test-Drive Assist
TestDrive-Assist is a unique tool developed by Original Software that has been specifically designed to work with the manual tester. Consequently, it's perfectly suited to the agile environment - something that has been has been recognised by Paul Herzlich of Ovum:
One area where OrigSoft's TestDrive-Assist can be appropriate is in unstable, changing circumstances. The two most notable situations are the first release of an application and in agile processes.
By recording your manual test, you may not have the benefit of full automation such as automatic data entry and validation. However you do get an audit trail and clear information for reproducing bugs. The ability to automatically migrate your manual test to an automated test may pay off immediately, but in any case, by the end of your scrum or iteration, it will form the foundation of a future automated test.
Whitepaper
The agile / QA myths blown apart
There's a lot of hype surrounding agile methodologies at the moment. QA teams need to know the real impact of an agile software development process. See our response to our top 10 favourite agile myths.
Testing in an agile Environment
Read a whitepaper from our partner AppLabs, which explores QA and testing activities in an agile environment and the critical characteristics of the testing team that ensure the success of development projects in an agile environment.
TestDrive-Assist
TestDrive-Assist could well be the answer to your agile software testing issues. Find out more about TestDrive-Assist at our dedicated manual testing website www.manualtesting.com
QualityMatters.tv
At QualityMatters.tv you can check as we build a regression test from scratch, run the test, change the application and re-run the test. All without touching the code and completed in a matter of minutes. See for yourself at QualityMatters.tv.
