ATDD (Acceptance Test-Driven Development)
// Definition
Extends TDD by writing acceptance tests collaboratively with the customer or product team before implementation begins. Aligns the team on what 'done' looks like in concrete, testable terms.
// Related terms
TDD (Test-Driven Development)
Write a failing test first, write the minimum code to make it pass, refactor. Drives design through tests rather than testing afterward — and produces a thorough unit test suite as a byproduct.
BDD (Behaviour-Driven Development)
Collaborative specification writing using human-readable scenarios (Given/When/Then) shared across product, dev, and QA. Often automated with Cucumber, SpecFlow, or similar tools.
UAT (User Acceptance Testing)
Verification by end users or business stakeholders that the system meets their real-world needs. The final validation gate before release.
Learn more · Manual Software Testing
Chapter 2 · Lesson 1: Understanding Requirements and Acceptance Criteria