User Acceptance Testing (UAT)
Final testing phase where end-users verify the software meets their requirements before deployment.
User Acceptance Testing (UAT), also known as beta testing or end-user testing, is the last step in the software development lifecycle before the product is released to the market. Its purpose is to validate that the software meets the business requirements and is usable by the end-users. Unlike system testing, which focuses on technical specifications and bug finding, UAT focuses on the workflow and usability from a user's perspective. It answers the question: 'Can the user use the system to do their job?' Failed UAT leads to deploying software that may technically work but doesn't solve the user's problem.
graph LR
Center["User Acceptance Testing (UAT)"]:::main
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Generated ELI5 content
🤓 Expert Deep Dive
Generated expert content
❓ Frequently Asked Questions
Who performs UAT?
UAT is performed by the end-users or the client who ordered the software, not the developers.
When does UAT happen?
It happens after system testing is complete and before the software is deployed to production.
Why is UAT checking important?
It ensures the developed solution actually fits the user's business needs and requirements.