CAPM Practice: Validate requirements through product delivery

ATDD (similar to BDD) defines acceptance tests before coding starts. Tests embody the acceptance criteria precisely, ensuring developers implement exactly what requirements specify. Passing tests validate requirements — failing tests reveal misunderstanding between requirements and implementation.

**Why not A:** ATDD is a collaborative technique involving the whole team (BA, developers, testers), not a methodology where only managers perform acceptance testing. The "driven" in ATDD refers to using acceptance tests to drive development, not to managerial oversight of testing.

**Why not B:** ATDD is not about testers driving all development decisions. It is a collaborative practice where acceptance tests are written before development begins, derived from requirements acceptance criteria. The tests guide development, but the entire team participates in defining them.

**Why not D:** Running tests automatically in production after deployment describes production monitoring or post-deployment testing. ATDD specifically involves writing acceptance tests before development starts, ensuring that development is guided by clearly defined acceptance criteria from the outset.