---
title: Acceptance test-driven development
slug: acceptance-test-driven-development
qid: 
snapshot: enwiki-001358200987
content_hash: 
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1358200987
tags: [23603337, 26083081, 26220375, 26839250, 39407882]
---

# Acceptance test-driven development

> [!note] Provenance
> Snapshot `enwiki-001358200987` · content root `…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1358200987> · Licensed CC BY-SA 4.0

Acceptance test–driven development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as specification by example (SBE), behavior-driven development (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 before implementation and allow customers to be able to converse in their own domain language. ATDD is closely related to test-driven development (TDD). It differs by the emphasis on developer-tester-business customer collaboration. ATDD encompasses acceptance testing, but highlights writing acceptance tests before starting any coding.

Acceptance test–driven development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as specification by example (SBE), behavior-driven development (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 before implementation and allow customers to be able to converse in their own domain language. ATDD is closely related to test-driven development (TDD). It differs by the emphasis on developer-tester-business customer collaboration. ATDD encompasses acceptance testing, but highlights writing acceptance tests before starting any coding. For the example requirement, the steps could be listed as: Given Book that has not been checked out And User who is registered on the system When User checks out a book Then Book is marked as checked out
