Acceptance Test-Driven Development (ATDD)

AKA: Test-Driven Development (SDD).
Example(s):
Counter-Example(s):
- Unit Testing,
- Integration Testing,
- Alpha Test,
- Beta Test.
See: Acceptance Testing, Test-Driven Development, Software Program, Software Requirement, Commercial Off-The-Shelf, Agile Software Development, Software Framework, Software Product, Software Maintenance, Source Code.

References

(Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/Acceptance_test–driven_development Retrieved:2021-10-27.
- Acceptance test–driven development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers.^[1] ATDD encompasses many of the same practices as specification by example (SBE), ^[2] behavior-driven development (BDD), ^[3] 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 prior to implementation and allow customers to be able to converse in their own domain language. ATDD is closely related to test-driven development (TDD). ^[4] It differs by the emphasis on developer-tester-business customer collaboration. ATDD encompasses acceptance testing, but highlights writing acceptance tests before developers begin coding.

↑ Pugh, Ken (2011). Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration. Addison-Wesley. ISBN 978-0321714084.
↑ Adzic, Gojko. (2009) Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing, Neuri Limited,
↑ Chelimsky, David, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, and Dan North. The RSpec Book: Behaviour Driven Development with RSpec, Cucumber, and Friends. The Pragmatic Bookshelf.
↑ Beck, Kent. Test Driven Development: By Example. Addison-Wesley Professional, 2002.