# Acceptance Test

> A test that checks a feature does what was asked for.

**Field:** Software Development  
**Category:** Testing & Quality  
**Also known as:** Acceptance Testing, Acceptance Tests, Acceptance Criteria Test

## Think of it like

Think of it like checking a cake against the order. Is it the kind the customer asked for?

## Definition

An acceptance test checks that a feature does what was asked for. It is written from the user's side, not the code's side. Each test matches one rule the feature must meet, called an acceptance criterion. If all the acceptance tests pass, the feature is done. They can be automated or done by hand.

## Example

The task says a shopper can pay with a saved card. The acceptance test logs in, picks the saved card and checks the order goes through.

## Why it matters

Code can pass every unit test and still not do what the user wanted. This test asks the real question.

## Common mistake

Writing acceptance tests after the code. Write them first, so everyone agrees on what done means.

## Three principles

- **User's view.** Checks what the user asked for.
- **Defines done.** All pass, feature finished.
- **Write it first.** Agree on it before coding.

## Related terms

- [User Acceptance Testing (UAT)](https://learn.benibix.com/term/development/user-acceptance-testing)
- [Acceptance Criteria](https://learn.benibix.com/term/business/acceptance-criteria)
- [Behavior-Driven Development (BDD)](https://learn.benibix.com/term/development/behavior-driven-development)
- [End-to-End Test (E2E)](https://learn.benibix.com/term/development/end-to-end-test)
- [Integration Test](https://learn.benibix.com/term/development/integration-test)

## Told apart from

- [Acceptance Test vs User Acceptance Testing (UAT)](https://learn.benibix.com/compare/acceptance-test-vs-user-acceptance-testing): People think user acceptance testing is just more acceptance tests, and it is not. An acceptance test is written by the team, often as code, to check a feature does what was asked. UAT is the last step before release, when real users or the client try the app by hand and sign it off. It finds a feature that works but is not what they needed.

![On the left, a developer's tests ask: does the code work? On the right, acceptance tests ask: does it do what was asked? Under the right side, a scenario card reads Given a cart with one mug, When I pay with a valid card, Then I see Thank you. At the far right, user acceptance testing, lit up, shows real users trying the app and signing it off before release.](https://learn.benibix.com/diagrams/dev3-acceptance.svg)

---

Source: https://learn.benibix.com/term/development/acceptance-test
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
