Editing Acceptance testing (section)

== Acceptance testing in extreme programming ==
{{Main|Extreme programming}}

Acceptance testing is a term used in [[agile software development]] methodologies, particularly [[extreme programming]], referring to the [[functional testing]] of a [[user story]] by the software development team during the implementation phase.<ref>{{Cite web |title=Introduction to Acceptance/Customer Tests as Requirements Artifacts |url=http://www.agilemodeling.com/artifacts/acceptanceTests.htm |access-date=December 9, 2013 |website=agilemodeling.com |publisher=Agile Modeling}}</ref>

The customer specifies scenarios to test when a user story has been correctly implemented. A story can have one or many acceptance tests, whatever it takes to ensure the functionality works. Acceptance tests are black-box system tests. Each acceptance test represents some expected result from the system. Customers are responsible for verifying the correctness of the acceptance tests and reviewing test scores to decide which failed tests are of highest priority. Acceptance tests are also used as [[Regression testing|regression tests]] prior to a production release. A user story is not considered complete until it has passed its acceptance tests. This means that new acceptance tests must be created for each iteration, or the development team will report zero progress.<ref>{{Cite web |last=Wells |first=Don |title=Acceptance Tests |url=http://www.extremeprogramming.org/rules/functionaltests.html |access-date=September 20, 2011 |publisher=Extremeprogramming.org}}</ref>

{{Expand section|date=May 2008}}