Agile testing
| Software development process |
|---|
| Core activities |
| Paradigms and models |
| Methodologies and frameworks |
| Supporting disciplines |
| Tools |
| Standards and BOKs |
Agile testing is a software testing practice that follows the principles of agile software development. Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customer at frequent intervals, working at a sustainable pace. Specification by example is used to capture examples of desired and undesired behavior and guide coding.
Overview
Agile development recognizes that testing is not a separate phase, but an integral part of software development, along with coding. Agile teams use a "whole-team" approach to "baking quality in" to the software product. Testers on agile teams lend their expertise in eliciting examples of desired behavior from customers, collaborating with the development team to turn those into executable specifications that guide coding. Testing and coding are done incrementally and interactively, building up each feature until it provides enough value to release to production. Agile testing covers all types of testing. The Agile Testing Quadrants provide a helpful taxonomy to help teams identify and plan the testing needed.
In contrast with other methodologies, Agile testing focuses on repairing faults immediately, rather than waiting for the end of the project. By doing so, costs are expected to go down.[1]
Tools
As companies grow, agile testing teams often rely on software testing tools to solve challenges that can ultimately speed-up the release of feedback making sure.[2] Most teams look for collaboration features, automated or customized reporting and finding ways to avoid repeated efforts. Choosing the right tool will depend on the requirements of each team. Pairing up with other Agile Lifecycle Development Tools, Agile testing tools can deliver effective results by coexisting in integrated environments. Such is the case for Atlassian Marketplace and Microsoft Visual Studio.[3]
Some test management tools are already supporting Agile testing by getting teams involved earlier in the SDLC to continuously build test scenarios as stories evolve. Teams often look for a solution that can deliver a combination of automated and manual testing.[4]
Further reading
- Lisa Crispin, Janet Gregory (2009). Agile Testing: A Practical Guide for Testers and Agile Teams. Addison-Wesley. ISBN 0-321-53446-8.
- Adzic, Gojko (2011). Specification by Example: How Successful Teams Deliver the Right Software. Manning. ISBN 978-1-61729-008-4.
- Martin, Kev (2016). The Agile Tester 2: Software testing in the agile world. CreateSpace. ISBN 978-1539646228.
- Ambler, Scott (2010). "Agile Testing and Quality Strategies: Discipline over Rhetoric". Retrieved 2010-07-15.
References
- ↑ BUILDING AND TESTING. (2014). BUILDING AND TESTING. In Agile Governance and Audit: An overview for auditors and agile teams (pp. 79–87). IT Governance Publishing. Retrieved from http://www.jstor.org/stable/j.ctt7zsx7z.14 Export Citation
- ↑ "Agile-Friendly Test Automation Tools/Frameworks - Test Obsessed". Retrieved 2016-06-29.
- ↑ "Gartner and Software Advice examine Agile Lifecycle Management Tools". Retrieved 2016-06-29.
- ↑ "Agile Testing Tools - Testing in Agile, Scrum and XP Projects". Retrieved 2016-06-29.
- Pettichord, Bret (2002-11-11). "Agile Testing What is it? Can it work?" (PDF). Retrieved 2011-01-10.
- Hendrickson, Elisabeth (2008-08-11). "Agile Testing, Nine Principles and Six Concrete Practices for Testing on Agile Teams" (PDF). Retrieved 2011-04-26.
- Huston, Tom (2013-11-15). "What Is Agile Testing?". Retrieved 2013-11-23.
- Crispin, Lisa (2003-03-21). "XP Testing Without XP: Taking Advantage of Agile Testing Practices". Retrieved 2009-06-11.
