Acceptance Test-Driven Development

From GM-RKB
Jump to: navigation, search

An Acceptance Test-Driven Development is a Specification by Example that ...



References

2016

  • (Wikipedia, 2016) ⇒ http://wikipedia.org/wiki/acceptance_test-driven_development Retrieved:2016-3-25.
    • 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, [2] Behavior Driven Development (BDD), [3] Example-Driven Development (EDD), and 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.
  1. Cite error: Invalid <ref> tag; no text was provided for refs named Pugh11
  2. Adzic, Gojko. (2009) Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing, Neuri Limited,
  3. 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.
  4. Beck, Kent. Test Driven Development: By Example. Addison-Wesley Professional, 2002.