What Is User Acceptance Testing (UAT)? | Vantage

User Acceptance Testing User Acceptance Testing (UAT) is the final phase of the software testing process, in which actual users or business stakeholders verify that a product or feature meets the agreed requirements and is ready for production release. UAT tests the system against real-world use cases and business workflows, not just technical correctness.

Why user acceptance testing matters

UAT is the last line of defense before general release. It catches issues that technical QA misses: edge cases in business workflows, missing requirements, and features that are technically functional but practically unusable. Catching these issues in UAT is far cheaper than discovering them after launch, when fixes require emergency releases and user trust is already damaged.

How it works

UAT follows a defined test plan: a set of test scenarios derived from business requirements and real user workflows. Testers (typically the Product Owner or actual end users) execute each scenario and record pass/fail. Failures are triaged: critical failures block release, minor failures may be deferred. UAT acceptance criteria are agreed upon before testing begins so that pass/fail decisions are objective.

Common mistakes

• Starting UAT without a written test plan (testers explore randomly instead of verifying requirements)

• Using only internal employees as UAT testers (they know the system too well and miss novice user issues)

• Not defining clear acceptance criteria before UAT begins (disputes arise about what 'pass' means)

• Treating UAT as a formality rather than a genuine gate

• Running UAT in a test environment that does not mirror production (environment-specific issues are missed)