Tester Driven Development
From Wikipedia, the free encyclopedia
 |
This article or section is missing citations and/or footnotes.
This article or section may use words or ideas of other works in its text without citing sources. Using citations to support claims outside the realm of elementary knowledge helps guard against copyright violations and factual inaccuracies. Please improve the article or discuss this issue on the talk page. Help on using footnotes is available. This article has been tagged since December 2006. |
| Software Development Process |
|---|
| This article is part of the Software Development Process series |
| Activities and Steps |
| Requirements | Architecture | Implementation | Testing | Deployment |
| Models |
| Agile | Cleanroom | Iterative | RAD | RUP | Spiral | Waterfall | XP |
| Supporting Disciplines |
| Configuration Management | Documentation | Project Management | User Experience Design |
Tester driven development is an Anti-pattern in software development. It should not be confused with Test Driven Development. It refers to any software development project where the Software testing phase is too long. The testing phase is so long that the requirements may change radically during software testing. New or changed requirements often appear as bug reports. Bug tracking software usually lacks support for handling requirements. As a result of this nobody really knows what the system requirements are.
Projects that are developed using this anti-pattern often suffer from being extremely late. Another common problem is poor code quality.
Common causes for projects ending up being run this way are often:
- The testing phase started too early;
- Incomplete requirements;
- Inexperienced testers;
- Inexperienced developers;
- Poor project management.
