UAT (User Acceptance Testing)
User acceptance testing (UAT) is the final round of testing in which the people who will actually use a system try it on real tasks, then confirm that it does what was agreed before it goes live.
Developers can test whether the software works as they built it. Only the people who will use it can say whether it works as their day demands. User acceptance testing, or UAT, is that second check, and it is your job as much as the developer's.
How UAT differs from QA testing
QA testing hunts for faults: broken buttons, wrong calculations, pages that crash. UAT asks a different question: with our real data, our real staff and our real habits, does this do the work we agreed? A system can pass every technical test and still fail UAT because a step that takes the clerk two clicks today now takes seven.
Why this round is your last cheap chance
This is the final point at which changes cost little. A gap found before launch is a small correction. The same gap found three months later, after staff have invented workarounds, is a project in itself. UAT sign-off is also the point where both sides agree that the delivered work matches the agreed scope.
An example: a pharmacy in Tirunelveli
Picture a pharmacy receiving new billing software. The developer proved that bills can be created. In UAT the counter staff try the awkward cases: returning half a strip, billing a medicine from a batch that expires next month, applying a senior-citizen discount and editing a bill after the customer has left. Two gaps appear, a missing discount rule and a returns screen that needs too many clicks. Both are cheap to fix now. See software for pharmacies for the wider picture.
How to run it well
- Write ten to fifteen scenarios from real working days, including awkward ones.
- Let the actual users do the testing, not only the owner.
- Record each issue and mark it as must-fix before launch or can wait.
- Re-test the fixes, then sign off in writing.
How UAT works with us
At VS Tech Builders the Develop step runs on weekly demos, much like an agile sprint cycle, so UAT is rarely the first time you see the software, and the 14 days after launch stay open for corrections. The process page shows where each step sits.
Common questions
Who should take part in user acceptance testing?
The people who will use the system every day, plus the owner or manager who is accountable for the result. A billing clerk, a stores keeper and an accountant will each find different problems. Testing by the owner alone misses the daily friction that staff feel. Give testers time away from their normal work, because rushed testing in spare moments finds very little.
What happens if UAT finds problems?
Each issue is recorded and sorted. Faults and gaps against the agreed scope are fixed before launch, then re-tested. New ideas that arise during testing are not failures; they are separate requests, to be priced and scheduled on their own. Launch happens once the must-fix list is clear and both sides have signed off in writing.
Read more
Tell us what you need. Get a fixed quote.
Describe your business and the problem in a few lines. We reply within one business day with an honest recommendation, a scope and a fixed price.