User acceptance testing
UAT · The test stage before delivery in which the customer or end users try the software with real business scenarios to decide whether to accept it.
- 01
Why it matters
Technical tests show the software works correctly; acceptance testing shows whether the job really gets done. Defining acceptance criteria in writing at the start of the project prevents the “this is not what we wanted” dispute at delivery. When acceptance testing ends, both sides agree on what is complete.
- 02
Example
A company's accounting team tries the new invoicing module by issuing a real month's invoices and comparing them with the old system. Once the amounts match, the module is accepted and goes live.
- 03
Common mistake
Having the development team do the acceptance testing, or not involving end users at all. Those who wrote the software cannot know the daily work of those who use it.
- 04
Related terms
Related services and guides
Let's talk about your project.
Tell us what you need; we will define the scope together.