ATDD (acceptance test-driven development) is a software development practice in which the conditions under which a feature is considered complete are written as acceptance tests before implementation begins, and development proceeds by making those tests pass. Because developers, testers, and business stakeholders define the tests together, it also serves as a way to align understanding of requirements.
It extends the unit-level discipline of TDD to user-facing acceptance criteria and is closely related to BDD and Specification by Example. The tests are often written in a near-natural-language format and automated with supporting tools.