Acceptance Testing
Acceptance testing verifies that a system satisfies business needs and is ready for release or delivery to users.
“A test level that focuses on determining whether to accept the system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Acceptance Testing?
Acceptance testing is the final test level performed to confirm that the system meets agreed acceptance criteria and is suitable for operational use. It focuses on validating business requirements rather than implementation details.
Purpose: Demonstrate that business requirements have been met.
Who performs it: Customers, users, or business representatives often participate.
Outcome: Successful acceptance testing increases confidence before release.
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. 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 Acceptance testing makes expected behavior testable before the feature is treated as finished.
Practice Questions
Question 1
Which statement BEST describes the primary goal of acceptance testing?
Question 2
A healthcare application has passed all system tests. Before releasing to production, real clinicians test the system using their actual daily workflows. What type of testing is this?
Test your knowledge with real ISTQB-style questions
You’ve learned Acceptance Testing. Test your understanding with topic-specific questions in our Mock Exams.