Agile testing
From Wikipedia, the free encyclopedia
| Software development process | |
| Activities and steps | |
|---|---|
| Requirements · Architecture Design · Implementation Testing · Deployment |
|
| Models | |
| Agile · Cleanroom · Iterative · RAD RUP · Spiral · Waterfall · XP · Scrum |
|
| Supporting disciplines | |
| Configuration management Documentation Quality assurance (SQA) Project management User experience design |
|
Agile testing is a software testing practice that follows the statutes of the agile manifesto, treating software development as the customer of testing.
Agile testing involves testing from the customer perspective as early as possible, testing early and often as code becomes available and stable enough from module/unit level testing.
Since working increments of the software is released very often in agile software development there is also a need to test often. This is often done by using automated acceptance testing to minimize the amount of manual labor. Doing only manual testing in agile development would likely result in either buggy software or slipping schedules because it would most often not be possible to test the whole software manually before every release.
[edit] References
Brett Pettichord. aJ-100: Real-Time Low-Power Direct Execution Microprocessor for the Java Platform. Retrieved on 2007-03-27.
