Testing · Definition
What UAT is, how it differs from QA, a seven-step process, a test case template and a sample checklist for a client portal.
Last updated: October 2026. Written by Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions.
Quick answer
User acceptance testing (UAT) is the final round of testing in which real users, or their representatives, check that a system works for them in realistic scenarios against agreed acceptance criteria. QA asks whether it was built correctly; UAT asks whether it meets business needs. Define criteria, write scenarios, choose testers from each role, use a test version with safe data, run and log results, prioritise issues, retest and sign off.
Key takeaways
- UAT = real users checking the product meets their needs against acceptance criteria.
- QA checks the build; UAT checks fitness for purpose.
- Use a test version with non-sensitive data and scenarios for every role.
- Classify issues; treat new ideas as change requests, not defects.
- Record formal sign-off before launch.
In this guide
What is user acceptance testing?
User acceptance testing, usually shortened to UAT, is the final round of testing in which the people who will actually use a system, or who represent them, check that it does what they need in realistic situations. It answers one question: does this work for us, in the way we really work, well enough to go live?
UAT vs other kinds of testing
| Type | Who does it | What it checks |
|---|---|---|
| Builder testing | The developer or builder | That features work as built |
| Quality assurance (QA) | A tester or the team | Functionality, errors, devices, performance and security against the specification |
| User acceptance testing | The client and real users | That the product meets business needs and acceptance criteria in real scenarios |
QA asks “was it built correctly?” UAT asks “was the right thing built, and does it work for us?” Both are needed. See what to cut before you build for how scope is set, since UAT checks against it.
Why does UAT matter?
- Builders unconsciously avoid the paths that break. Real users find them.
- It catches misunderstandings between what was specified and what was needed.
- It gives the client a structured way to say yes.
- It is far cheaper to find problems before launch than after.
- It records the client’s acceptance, which supports payment and handover.
How to run UAT in seven steps
- Define acceptance criteria. Use the user stories and PRD. Each key flow should have clear conditions for being done.
- Write test scenarios. Real tasks in plain language, such as “A client uploads a document and the assigned staff member is notified.”
- Choose testers. People who will use the product, from each role.
- Prepare a test environment. Use a test version with realistic, non-sensitive data, never real personal data unless it is properly protected.
- Run the scenarios. Testers follow the steps, record results and note anything confusing, not just anything broken.
- Log and prioritise issues. Fix blockers first, and decide what can wait.
- Retest and sign off. Confirm fixes, then record formal acceptance.
UAT test case template
Test case
ID: UAT-___ Role: ________ Scenario: ________
Preconditions: ________
Steps: 1. ________ 2. ________ 3. ________
Expected result: ________
Actual result: ________ Pass / Fail: ____
Notes and screenshots: ________
A sample UAT checklist for a client portal
| Area | Scenarios to test |
|---|---|
| Access | Register, log in, reset password, log out |
| Client tasks | Upload a document, respond to a request, send a message, view status, view an invoice |
| Staff tasks | Review an upload, request changes, update status, see overdue items |
| Admin tasks | Add a user, deactivate a user, change a role |
| Privacy | Two clients try to open each other’s records. Restricted actions are blocked for low-permission roles |
| Notifications | Emails arrive with correct content and working links |
| Edge cases | Large files, empty fields, wrong inputs, slow connections |
| Devices | Phone, tablet and desktop |
How should you classify issues?
| Severity | Meaning | Typical handling |
|---|---|---|
| Blocker | Prevents a key task or exposes data | Must fix before launch |
| Major | Key feature works badly or has a poor workaround | Fix before launch if possible |
| Minor | Small annoyance or cosmetic issue | Schedule after launch |
| Suggestion | A new idea outside the agreed scope | Add to the backlog; may need a change request |
The last row matters: UAT often generates new ideas. Treat them as change requests, not defects. See how to avoid scope creep.
What are common UAT mistakes?
- Using the builder as the only tester.
- Vague criteria, so nobody knows what pass means.
- Testing only the happy path.
- Using real sensitive data in a test environment.
- No deadline for feedback, so UAT drags on.
- Treating every suggestion as a defect.
- Skipping formal sign-off.
How do we approach it?
At Simple Automation Solutions, builds run on a separate test version with regular demos, and testing includes trying to access other users’ data with multiple accounts. We encourage clients to test with a small pilot group before wider launch. See our security guide and our process from discovery to launch. Builds start at $3,500 and typically launch in 2 to 6 weeks.
Frequently asked questions
What does UAT stand for?
User acceptance testing.
What is the difference between QA and UAT?
QA checks that the product was built correctly against the specification. UAT checks with real users that it meets their needs in realistic scenarios.
Who should do user acceptance testing?
The people who will use the product, or people who represent them, from each role, not only the developer.
How long does UAT take?
It depends on scope. For a small app, a few days of focused testing and fixing is typical. Set a deadline for feedback.
What happens after UAT?
Fix blockers and major issues, retest, record sign-off and plan the launch. Minor items and new ideas go on a backlog.
About to launch an app and want it properly tested?
Email us what it does and when you plan to launch. We will help you plan UAT and a safe rollout.
Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions
About Simple Automation Solutions (SA Solutions)
Simple Automation Solutions is a Bubble.io development studio led by Athar Ahmad, a Certified Bubble.io Developer and Tech Architect. It builds web and mobile apps, client portals and SaaS products for founder-led businesses such as law firms, accounting firms, boutique agencies and consultants. Services include a free 30-minute Idea Audit, a $345 Discovery Sprint (a Product Requirements Document delivered within 24 hours, credited toward the build) and builds starting at $3,500. Website: sasolutionspk.com.
