What is a UAT tester?
A UAT tester is someone who checks that software does the job it was built for, before it goes live. They work through real tasks and report what does not behave the way the job requires.
Most UAT testers are not professional testers. They are the people who will use the software: finance staff testing an invoicing change, support agents testing a new console, a client's team testing what an agency built for them.
What a UAT tester actually does
- Works through the tasks they would do in a normal week, using the new software.
- Notes anything that blocks the task, produces the wrong result, or is unclear enough to slow them down.
- Reports each one with enough detail that someone else can see the same thing.
- Re-checks fixes once they land.
- Says whether the software is acceptable, which is the part that carries their name.
What makes a good UAT tester
They know the job, not the software. Someone who understands how the work actually gets done will notice when a screen assumes it happens in a different order.
They test the awkward cases. A tester who follows the happy path confirms it works. A tester who tries the refund on the order that was partially returned finds the problem.
They describe rather than diagnose. "It's broken" and "the database is wrong" are both unhelpful. What they clicked, what they expected, what happened instead is what the team needs.
They report as they go. Notes written at the end of the day lose the detail that makes a report reproducible.
What does a UAT test case look like?
A UAT test case describes one real task, the result the business expects, and space for what the tester saw. Here is one for an order system you're building:
- Task: refund an order that was partially returned.
- Starting point: an order of three items, one of them returned last week.
- Steps: open the order, choose "Refund", select the returned item, confirm.
- Expected result: the customer is refunded for one item only, and the order shows as partially refunded.
- Actual result: filled in by the tester.
- Pass or fail: with a link to the issue report if it failed.
The steps say what to do, not which buttons to click in which order. A tester who has to follow a click script stops noticing whether the task makes sense.
What a useful UAT report contains
- What they were trying to do.
- The steps they took.
- What they expected.
- What actually happened.
- The technical context: browser, device, screen size, any error on screen.
The last one is where most UAT rounds lose time. Asking a non-technical tester for their browser version produces either a guess or a shrug, and the developer cannot reproduce the issue without it. Capturing it automatically removes an entire category of back and forth.
UAT tester vs QA tester
A QA tester is a professional whose job is finding defects against a specification, often using test cases and automation. A UAT tester is a business user checking whether the result is usable for the work they do. QA runs first and is thorough. UAT runs last and is realistic.
What comes first, UAT or QA?
QA comes first. The QA team tests the build against the specification, and once the defects they find are fixed, the build moves to a UAT environment for business users to accept. Running UAT on a build that hasn't passed QA wastes the testers' time on defects someone else should have caught.
What is the difference between UAT and usability testing?
Usability testing checks whether people can use a design easily, and UAT checks whether the finished software supports the work it was built for and ends in a formal sign-off.
Usability tests usually run earlier, often on prototypes, with a researcher watching a handful of participants. Jakob Nielsen of Nielsen Norman Group argued in 2000 that five users per round find most usability problems. UAT runs at the end on the real build, and the testers' approval decides whether it ships.
Is UAT tester a job title?
Sometimes. Organisations that run large ERP, banking or public-sector systems hire UAT testers, UAT analysts or UAT coordinators who plan test rounds, write test cases with the business and manage sign-off. In most companies, though, UAT tester is a temporary role that business users take on for the length of a release.
UAT testers in enterprise product teams
An enterprise release can have dozens of UAT testers from different departments, regions and client accounts, and few of them test for a living. The coordinator's job is to make their reports comparable. Every report should follow the same structure and carry the same technical details, so the team can count how many testers hit the same issue.
The other job is traceability. When a release is accepted, someone will later ask who tested which task and what they found. Reports kept in one place, each linked to the tester and the step, answer that without a hunt through email threads.
How Usersnap helps UAT testers
A tester clicks the widget, points at the problem, writes a sentence and submits. Usersnap attaches the annotated screenshot and the browser, operating system and screen size automatically, so the tester never has to know what any of that means. Screen recordings cover anything a screenshot cannot capture. Reports can be sent to Jira, Linear or Azure DevOps, so they reach the developer without anyone re-typing them.
UAT tester FAQ
Who should be a UAT tester?
Someone who does the job the software supports. Business users, subject matter experts or the client's own staff, rather than developers or the QA team.
What skills does a UAT tester need?
Knowledge of the work, attention to the awkward cases, and the discipline to describe what happened rather than guess at the cause. Technical skill is not the requirement.
What is the difference between a UAT tester and a QA tester?
QA testers check the software against the specification. UAT testers check it against real work. QA finds defects, UAT finds wrong assumptions.
What tools do UAT testers use?
Usually three kinds: a test management tool or shared spreadsheet for the test cases, an issue tracker such as Jira for the defects, and a feedback tool that captures a screenshot and the browser details with each report.
Related terms
See how UAT testers report an issue without answering technical questions.
.svg)
