✅User Acceptance Testing

NEW

Also known as: UAT

Formal testing by end users to verify the system meets business acceptance criteria before go-live.

DESCRIPTION

User Acceptance Testing (UAT) validates that a system satisfies user needs and business processes. It occurs near the end of the delivery cycle and precedes production release. UAT testers execute scenarios and scripts derived from requirements and real-world workflows. Success criteria include functional correctness, usability, and readiness for production. UAT often results in formal sign-off by business stakeholders. In data and BI projects, UAT verifies KPIs, report logic, and data quality against expectations. Clear test data, traceable requirements, and defect triage are essential. UAT complements system, integration, and regression testing by focusing on business acceptance.

ALTERNATIVE DEFINITIONS

Wikipedia

User acceptance testing (UAT) consists of a process of verifying that a solution works for the user.

Concise definition emphasizing verification from the user’s perspective.

Source

Atlassian

User acceptance testing (UAT) is the final phase of the software testing process and involves real-world users testing the software to make sure it can handle required tasks in real-world scenarios.

Highlights real-world scenarios and positioning as the final testing phase.

Source

RELATED TERMS

Acceptance Testing Test Plan Test Case Requirements Validation Regression Testing Sign-off Quality Assurance Go-Live

COMPETING TERMS

System Integration Testing

RELATIONS

• Broader: Testing

KNOWLEDGE AREAS

Testing & Validation Software Engineering Data Products

TARGET AUDIENCE

Software Developer BI Specialist Information Analyst Data Management Consultant Data Governance Manager AI Product Manager

EXTERNAL SOURCES

• Wikipedia - Acceptance testing
• Atlassian - Guide to testing types including UAT
• ISTQB - Glossary entry for UAT
• Microsoft - Acceptance criteria guidance

TOP QUESTIONS

Who participates in User Acceptance Testing?

Business users, product owners, and subject matter experts execute tests. QA facilitates and engineers support defect resolution. Stakeholder sign-off confirms readiness.

Category: Example

How is UAT different from System Integration Testing?

SIT validates interfaces and end-to-end flows from a technical standpoint, while UAT focuses on business goals and acceptance criteria defined by users.

Category: Misunderstanding

What makes UAT effective?

Clear acceptance criteria, realistic test data, traceability to requirements, and a defined defect process. Training testers and timeboxing cycles are also critical.

Category: Best practices

What are common mistakes in UAT?

Vague acceptance criteria, inadequate test data, and insufficient user involvement lead to missed issues. Late UAT scheduling risks project delays.

Category: Mistakes

When does User Acceptance Testing happen?

It typically occurs after system testing and before production deployment, allowing final validation and sign-off by business stakeholders.

Category: Process

How is UAT managed?

Use a test plan, scenarios, and scripts aligned to requirements. Track defects, retest fixes, and document sign-off with clear go/no-go criteria.

Category: Management

What is the risk of skipping UAT?

Systems may meet technical specs but fail business users’ needs. Post-release issues can erode trust and increase remediation costs.

Category: Risks

What is a hot topic in UAT for data projects?

Automated test data generation and executable specifications that connect metrics to acceptance criteria are gaining traction.

Category: Topic

How do you choose UAT scenarios?

Prioritize critical business workflows, edge cases, and regulatory requirements. Include both happy paths and failure conditions.

Category: Requirements