Skip to content
BENIBIX Learn

Acceptance Test vs User Acceptance Testing (UAT)

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.

Development🧪 Testing & Quality

Acceptance Test

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

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.
Full entry
Development🧪 Testing & Quality

User Acceptance Testing (UAT)

Real users try the app before release and sign it off.

User acceptance testing is when real users or the client try the app before release. They use it for their real tasks, in a setup close to the live one. They check it does the job they need. If it does, they sign it off, and the release can go ahead. It is often the last test before launch.

Example
Before the new booking app goes live, ten clinic staff use it for a week. They sign it off once every booking task works.
Why it matters
Only the people who will use it can say if it truly does their job.
Full entry

In one line

Acceptance Test
A test that checks a feature does what was asked for.
User Acceptance Testing (UAT)
Real users try the app before release and sign it off.