II.
Methodology overview
Reference · livemethodology:acceptance-test-driven-development
Acceptance Test-Driven Development (ATDD) overview
A practice where the whole team collaboratively defines acceptance criteria before development begins, then uses those criteria to drive implementation. Unlike BDD which emphasizes behavior language, ATDD focuses on concrete examples that become automated acceptance tests, ensuring every feature meets explicit customer-defined expectations before being marked complete.
Attributes
displayName
Acceptance Test-Driven Development (ATDD)
description
A practice where the whole team collaboratively defines acceptance criteria
before development begins, then uses those criteria to drive implementation.
Unlike BDD which emphasizes behavior language, ATDD focuses on concrete
examples that become automated acceptance tests, ensuring every feature
meets explicit customer-defined expectations before being marked complete.
methodologyKind
quality-focused
origin
Ken Pugh
yearIntroduced
2003
Outgoing edges
applies_to2
- domain:software-engineering·DomainSoftware Engineering
- domain:qa-testing·DomainQA/Testing
Incoming edges
None.