Operational Acceptance Testing
Operational Acceptance Testing (OAT) verifies that a system is ready for production by evaluating operational processes such as backup, recovery, monitoring, security, and maintenance.
“A type of acceptance testing performed to determine if operations and/or systems administration staff can accept a system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Operational Acceptance Testing?
OAT ensures that operational support procedures are in place before the system is deployed into the production environment.
Production readiness: Confirms operational capabilities.
Operational processes: Includes backup, restore, monitoring, and maintenance.
Deployment support: Reduces operational risks after 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. Operational 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 Operational acceptance testing makes expected behavior testable before the feature is treated as finished.
Practice Questions
Question 1
Which statement BEST describes Operational acceptance testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Operational acceptance testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Operational Acceptance Testing. Test your understanding with topic-specific questions in our Mock Exams.