QA Foundations
User acceptance testing
Also known as: UAT
User acceptance testing (UAT) is the final phase where real users verify that software meets business requirements and works in real-world scenarios before release.
Where earlier testing asks whether the software works, UAT asks whether it does what the business actually needs. It is the sign-off gate before go-live, usually performed by end users, product owners, or QA acting as users, against agreed acceptance criteria.
Common forms include alpha testing (internal, early), beta testing (external users, pre-release), and contract or regulatory acceptance testing. UAT failures often reveal requirement gaps rather than code defects, which is why running it late but before release is so valuable.
- The final sign-off: real users validate against business acceptance criteria.
- Checks fitness for purpose, not just correctness.
- Forms include alpha, beta, and contract acceptance testing.
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed August 2, 2026