Agile testing is a software testing practice, which follows the principles of the agile manifesto, which stresses the test from the perspective of customers who want to use the system. Agile testing is not tightly defined testing procedures, but instead focus on testing newly developed code in an iterative manner until quality is achieved from an end customer’s perspective. In other words, the emphasis shifted from “testers as quality police” to something more like “the entire project team working towards the demonstration of quality.”
Agile testing involves testing from the customer perspective, as early as possible, test early as code becomes available and stable enough from the module / unit level test.
Since in agile software development we have too many frequent builds, there is also a need to test frequently. This is usually done through automated acceptance tests to minimize the amount of manual labor involved. Doing only manual testing in agile development can result in either buggy software or slipping schedules, because it might be impossible to test the whole build manually before each release.
- Pettichord, Bret. “Agile Testing What is it? Can it work?“. http://www.io.com/~wazmo/papers/agile_testing_20021015.pdf. Retrieved 2008-12-11.
- Hendrickson, Elisabeth (2008-08-11). “Agile Testing, Nine Principles and Six Concrete Practices for Testing on Agile Teams“. http://testobsessed.com/wordpress/wp-content/uploads/2008/08/AgileTestingOverview.pdf. Retrieved 2008-09-03.
- Parkinson, Shane (2008-11-26). “Agile Methodology“. http://agiletesting.com.au/agile-methodology/agile-methods-and-software-testing/. Retrieved 2008-11-26.
- Egan, Patrick (2008-12-15). “Video: How does agile affect testing“. http://www.agilejournal.com/component/option,com_seyret/Itemid,0/task,videodirectlink/id,49/. Retrieved 2008-11-26.
- Crispin, Lisa (2003-03-21). “XP Testing Without XP: Taking Advantage of Agile Testing Practices“. http://www.methodsandtools.com/archive/archive.php?id=2. Retrieved 2009-06-11.