An acceptance test checks whether a system, feature, or work product meets defined acceptance criteria.
The test uses specific inputs, actions, and expected results. Therefore, stakeholders can decide whether to accept or reject the tested result.
Teams create acceptance tests from requirements or user stories. First, they define the expected behaviour. Then, they compare the actual result with that expectation. As a result, acceptance tests provide clear evidence of requirement fulfilment.
Acceptance tests may use manual or automated procedures. For example, a test can verify that a user completes a payment successfully. Moreover, each test should focus on one observable result.
Acceptance tests support shared understanding between stakeholders, developers, and testers. In addition, they reduce ambiguity and provide a basis for final acceptance.
Unlike an acceptance criterion, an acceptance test describes the actual verification procedure. Thus, the criterion defines the condition, while the test checks that condition.
« Back to Glossary Index