← Back to Home

Acceptance Testing (UAT)

Acceptance Testing, commonly called User Acceptance Testing (UAT), is the final level of testing performed to validate that the software meets business requirements and is acceptable for release.

UAT answers: “Is this system acceptable to the business and end users?”

1. Definition

Acceptance Testing, commonly called User Acceptance Testing (UAT), is the final level of testing performed to validate that the software meets business requirements and is acceptable for release.

UAT answers: “Is this system acceptable to the business and end users?”

2. Purpose of Acceptance Testing

  • Validate business requirements
  • Ensure the system supports real-world workflows
  • Confirm readiness for production release
  • Provide business sign-off

3. Who Performs UAT

  • Business users
  • Product owners
  • End users
  • Clients or customers

Manual testers’ role:

  • Support and coordinate UAT
  • Prepare UAT test cases
  • Provide environments and data
  • Log and track defects

4. Scope of UAT

UAT focuses on:

  • Business workflows
  • End-to-end scenarios
  • Data correctness
  • Usability from business perspective

UAT does not focus on:

  • Detailed technical testing
  • Internal code logic

5. Types of Acceptance Testing (Conceptual)

  • Business Acceptance Testing (BAT)
  • User Acceptance Testing (UAT)
  • Regulatory Acceptance Testing
  • Contract Acceptance Testing

6. Entry & Exit Criteria (UAT)

Entry Criteria

  • System testing completed
  • Stable build deployed
  • No critical system defects
  • UAT scenarios prepared

Exit Criteria

  • Business approval received
  • Critical UAT defects resolved
  • Sign-off provided

7. UAT vs System Testing

Aspect System Testing UAT
Performed by QA/Testers Business/Users
Focus Requirements Business acceptance
Environment Test UAT / Prod-like
Goal Find defects Accept product

8. Real-Time Example

Payroll system UAT checks:

  • Salary calculation accuracy
  • Tax deductions
  • Payslip generation
  • Compliance with regulations

9. Common UAT Defects

  • Business rule mismatches
  • Missing reports
  • Incorrect workflows
  • Usability issues

10. Common Mistakes in UAT

  • Treating UAT as another system test
  • Inadequate user involvement
  • Poor test data
  • Late defect resolution

11. Interview-Ready Answers

Short answer:

Acceptance testing is performed to validate that the software meets business requirements and is ready for release.

Detailed answer:

UAT ensures the application supports real business scenarios and provides formal business approval before going live.

12. Key Takeaway

Acceptance Testing ensures business confidence and readiness, not just technical correctness.