Acceptance Test
Acceptance tests, also called user acceptance tests or UAT, are tests that verify that the software meets the business requirements and satisfies the expectations of the end user, before it is accepted and released.
Acceptance tests are usually the final phase of testing, run after unit, integration, and functional tests have already passed. They are often written from user stories or business specifications, using tools such as Behat or Codeception, sometimes in a natural-language format like Gherkin, so that non-developers, such as product owners or clients, can read and validate them.
Acceptance tests focus on whether the software does what the business needs, not on how it is implemented internally; in that sense, they are a form of black box testing.
See Also
- A guide to acceptance testing
- Difference Between Unit, Functional, Acceptance, and Integration Tests