User Acceptance Testing
User Acceptance Testing (UAT) is the test level in which intended users or customers verify that the software satisfies business needs and is ready for operational use.
“A type of acceptance testing performed to determine if intended users accept the system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is User Acceptance Testing?
UAT provides confidence that the system supports real-world business processes before deployment.
Business focused: Confirms business requirements are satisfied.
Performed by users: End users or customer representatives execute tests.
Release decision: Supports final acceptance before deployment.
Real World Example
A healthcare scheduling team is building a feature that lets patients book follow-up appointments after a consultation.
Developers, testers, clinicians, and product owners may all believe they understand the request while imagining different rules. User acceptance testing gives the team a shared way to confirm intent.
The tester turns clinical and business expectations into concrete examples, such as eligible appointment windows, unavailable doctors, and messages shown when no slot is open.
The team prevents late rework because User acceptance testing makes expected behavior testable before the feature is treated as finished.
Practice Questions
Question 1
Which statement BEST describes User acceptance testing in the context of ISTQB terminology?
Question 2
A tester needs to explain User acceptance testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned User Acceptance Testing. Test your understanding with topic-specific questions in our Mock Exams.