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.
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.
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.
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.