What is user acceptance testing (UAT)? Definition and examples
The final check before release, where the people who will use the software, or the client, confirm it does what they need.
User acceptance testing (UAT): The final check before release, where the people who will use the software, or the client, confirm it does what they need.
UAT happens after developers and QA have tested. Clients or real users try real tasks and sign off, or report what has to change.
The hard part is collecting their findings clearly: which page, what they did, what they expected.
Example
- A client checks every page of a new site before launch.
- Finance staff try the new expense flow with real receipts.
A simple UAT plan
- 1
Agree what “done” means
Write the tasks the client or users must be able to complete, such as “book a stay for two nights and pay”.
- 2
Give testers the build and the tasks
A staging site or a TestFlight build, plus the list. Keep it short enough to finish in one sitting.
- 3
Collect issues in one place
Every problem with the page or screen attached, not in a long email thread.
- 4
Fix, re-test and sign off
Reply to each issue when fixed, ask the tester to check, and record the sign-off.
UAT vs QA
QA checks that the software works as built. UAT checks that it does what the people paying for it need. QA is usually done by the team; UAT by the client or real users.
Where Bopmigo fits
Testers report from the page they’re testing, with the details attached, and you reply where they reported.
Questions
Who should do UAT?
The people who will use it, or the client who has to sign it off. Not the team that built it.
Who does user acceptance testing?
The client, product owner or a group of real users, not the developers who built it.
How long should UAT take?
Often a few days to two weeks, depending on how many tasks and testers there are.