Skip to main content
Legia

Apps & Software

What is UAT (User Acceptance Test)?

Also called user acceptance testing, acceptance testing.

Short definition

UAT (user acceptance test) is the final testing stage before an application goes into use, when users from the company try the application with real work scenarios to decide whether to accept it.

How it works

Before UAT begins, the company and the development team agree on a list of test scenarios derived from the requirements document, for example “warehouse staff record incoming goods in two different units”. Designated users run those scenarios in the staging environment, mark the ones that pass, and record the ones that fail along with the steps. After fixes and retesting, the company signs an acceptance report. The data used should resemble day-to-day data, including rare but important cases such as product returns or canceled transactions.

Why it matters

UAT is the point at which the company declares the application matches what it ordered. In many contracts, UAT is a condition for handover, milestone payments, and the start of the warranty period. That is why pass criteria need to be clear from the start, not decided while testing is under way. The company also needs to set aside testers' time and appoint one person authorized to sign off on acceptance.

Common mistakes

The testers are not the actual users, for example only managers who rarely use the system. The UAT window is too short because it is scheduled alongside routine work. New feature requests are mixed in with bug reports, so handover is delayed indefinitely. Keep the two apart: bugs are fixed within scope, while new requests are logged for the next phase, with their scope and schedule discussed separately.

Related Legia service Web Application Development Service portals, document archives, and CMS dashboards with role-based login, built in stages with source code that belongs to you.