Implementing Continuous Testing in Agile

by Nataliia Vasylyna | June 21, 2016 5:41 am

The Agile methodology implies continuous delivery of fully functioning software portions. A reasonable question appears: If the development process is continuous, shouldn’t the software testing process be continuous as well?

The logic suggests it should. In Agile, it’s wrong to start testing just a few days before release. An experienced software tester knows that testing should start early and continue throughout the entire development process. To accomplish that, a team should consider choosing automated testing[1].

How Can Automation Help to Implement Continuous Testing?

• Automated testing simplifies and accelerates the process of receiving instant feedback on the product’s status. This factor is crucial for effective continuous testing.
• If developers are somehow engaged in test automation during the development process, their relationships with testers will be more fruitful and honest.
• In most cases, automation is applicable not only to regression tests but also to non-functional tests.
• Automated tests can and should be executed on a Continuous Integration server.
• It is possible to write a suite of quick regression tests and run it every time a product is updated.
• Test automation plays a crucial role in the success of unit testing[2].
• Similarly to testing, deployments and time-consuming manual tasks can also be automated.

In addition to the above, it is important to understand that both performance testing[3] and security testing should also be integrated into the Agile process from its start.

Related Posts:

• Agile Testing: Crossing the T’s[4]
• Agile Team: Types of Self-management[5]
• Assessing Success of Agile Project[6]

Source URL: https://blog.qatestlab.com/2016/06/21/implementing-continuous-testing/

---