Acceptance test-driven development: Difference between revisions

Revision as of 20:42, 7 September 2019

Revision as of 01:22, 29 October 2019

Line 8:

== Overview ==

Acceptance tests are from the user's point of view – the external view of the system.<ref name="Pugh11" /> They examine externally visible effects, such as specifying the correct output of a system given a particular input. Acceptance tests can verify how the state of something changes, such as an order that goes from "paid" to "shipped". They also can check the interactions with interfaces of other systems, such as shared databases or web services. In general, they are implementation independent, although automation of them may not be.<ref>Melnik, Grigori, and Frank Maurer. {{cite web | url = http://www.springerlink.com/content/34w2q2561k471175/ | title = Multiple Perspectives on Executable Acceptance Test-Driven Development | accessdate = 2013-04-15}}</ref><ref>Koskela, Lasse. (2007) Test Driven: [[TDD | test driven development]] and Acceptance TDD for Java Developers. Manning Publications</ref>

=== Creation ===