User Acceptance Testing (UAT)
Definition
A user acceptance test checks whether a solution fulfills the agreed tasks from the perspective of its users.
Future users or domain experts work through realistic scenarios and compare the results with acceptance criteria. Technically passed individual tests do not replace this domain-specific review.
Simply explained
Like a test drive on the routes for which a vehicle is actually needed.
Why it matters in practice
This makes domain-specific gaps visible before handover.
Example from business
Hypothetical example: Employees check whether they can fully process a customer order including special cases.
Limits and pitfalls
- Unclear criteria, unrealistic test data, and mere clicking through lead to weak acceptance.
Origin & history
User acceptance is one of the established testing phases in software development.
Use in mid-sized companies
- Accept new portals and automations with real workflows.
Frequently asked questions
Do all internal lines of code have to be checked for this?
No, the focus is on domain-observable results.
Sources
- Glossary · ISTQB: Glossary –
Editorially reviewed on: