Acceptance test-driven development

<p>Acceptance test–driven development (ATDD) is a <a href="/facts/Software_development/UUfsAaYY">development</a> methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as <a href="/facts/Specification_by_example/pBzWBG0e">specification by example</a> (SBE), <a href="/facts/Behavior-driven_development/9NlSxLxh">behavior-driven development</a> (BDD), example-driven development (EDD), and support-driven development also called story test–driven development (SDD). All these processes aid developers and testers in understanding the customer's needs prior to implementation and allow customers to be able to converse in their own domain language.
</p><p>ATDD is closely related to <a href="/facts/Test-driven_development/fDCzXkt1">test-driven development</a> (TDD). It differs by the emphasis on developer-tester-business customer collaboration. ATDD encompasses <a href="/facts/Acceptance_testing/xlDUeQ0M">acceptance testing</a>, but highlights writing acceptance tests before developers begin coding.
</p>

Acceptance test-driven development open-in-new

Acceptance test-driven development