Tester Driven Development
This article does not cite any sources. (May 2018) (Learn how and when to remove this template message)
Tester-driven development, or bug-driven development is an anti-pattern where the requirements are determined by bug reports or test results rather than for example the value or cost of a feature.
The term itself is a tongue-in-cheek reference to Test-driven development, a widely used methodology in Agile software practices. In test driven development tests are used to drive the implementation towards fulfilling the requirements. Tester-driven development instead shortcuts the process by removing the determination of requirements and letting the testers (or the QA team) drive what they think the software should be through the testing (or QA) process.
|This software-engineering-related article is a stub. You can help Wikipedia by expanding it.|