Jump to content

Tester-driven development

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Soulkeeper (talk | contribs) at 09:43, 31 January 2019 ({{Merge|Bug-driven development}}). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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.