Skip to main content
Skip to content

User Acceptance Testing (UAT): Process, Checklist, Template and Examples

Top FAQ's on User Acceptance Testing

User acceptance testing (UAT) is the final phase of software testing, where the people who will use the system check that it does what the business needs before it goes live. Real users or business representatives run realistic scenarios in a production-like environment and decide whether to accept the software. If they find problems that block their work, the release waits.

This guide is the hub for everything on Testmetry about UAT. It explains the basics, the process step by step, entry and exit criteria, how to write acceptance criteria and test cases, and the mistakes that cause UAT to fail. Use the links to go deeper on a template, a checklist, examples or interview questions.

Who this UAT guide covers

What is user acceptance testing?

User acceptance testing validates the finished system against business needs, from the user’s point of view. Earlier phases ask “did we build it right?” UAT asks “did we build the right thing, and can people do their jobs with it?” It usually happens after system integration testing and before deployment to production. It is a type of functional testing, not a verification activity such as a review or a static analysis, because it runs the actual software.

The purpose of UAT is to confirm the software meets user needs, to check usability and workflows end to end, and to reduce the risk of failures in production, because business users validate the product before it ships. A short video on user acceptance testing gives a quick overview.

UAT

UAT full form

UAT stands for User Acceptance Testing. Some teams call it end-user testing or application testing, and a large share of UAT is business acceptance testing. For more detail on the term, see the UAT full form in testing.

Types of acceptance testing

  • User acceptance testing: business users test the workflows they will use.
  • Business acceptance testing: checks the software meets business goals and processes.
  • Contract acceptance testing: checks the product against the terms of a contract.
  • Regulatory or compliance acceptance testing: checks the software meets legal or industry rules.
  • Operational acceptance testing: checks backup, recovery, maintenance and support readiness.
  • Alpha and beta testing: internal and external pre-release testing. See the difference between alpha and beta testing and what a beta version is.

UAT vs system testing

System testing User acceptance testing
Question answered Does the system meet its specification? Does the system meet the business and user need?
Done by QA and test engineers Business users, product owners, subject matter experts
Test basis Technical and functional requirements Business requirements and real workflows
Environment Test environment Production-like environment
Outcome Defects fixed by developers Go or no-go sign-off

Who performs UAT?

UAT is performed by end users or representatives of the target user group, with support from the project team.

  • Business users and subject matter experts: run the scenarios and judge the result.
  • Product owner or business sponsor: sets acceptance criteria and gives final sign-off.
  • UAT coordinator or test lead: plans the cycle, organises users, tracks progress and reports.
  • QA engineers: help design the test cases and support the users, especially in the first cycle.
  • Developers: triage and fix the defects that UAT reveals.

In some projects the end users only run the tests, while test engineers design the test cases from the requirements.

UAT entry criteria

Start UAT only when these are true:

  • System integration testing is complete, and severity 1 and 2 defects found there are fixed.
  • The UAT environment is stable and matches production as closely as practical.
  • Test data is ready and does not expose real customer information.
  • Acceptance criteria and test cases are written and agreed.
  • Users have been identified, trained and given time to test.

The UAT process step by step

  1. Plan UAT. Define scope, schedule, participants, environment and the decision rule for sign-off.
  2. Define acceptance criteria. Agree what “accepted” means for each requirement.
  3. Design test cases and scenarios. Cover end-to-end business workflows, positive and negative paths.
  4. Prepare the environment and data. Use sanitised or synthetic data, never a raw copy of production.
  5. Run the tests in cycles. Users execute scenarios and log results and defects.
  6. Triage and fix defects. Prioritise by business impact, fix, and retest.
  7. Report and decide. Compare results with the exit criteria and give a go or no-go decision.
  8. Sign off. Record the acceptance formally, with any known issues and workarounds.

For the full walk-through, with the four phases, best practices and the mistakes to avoid, read the UAT process guide.

Test cycles

UAT usually runs as a series of test cycles, which are coordinated test events made of tasks described in detailed test scripts. Cycles keep the work structured, help manage time and users, and give a chance to gather feedback and act on it before the next cycle. A common pattern is a first cycle to find the main problems, a second to retest fixes and cover new areas, and a final confirmation cycle.

The UAT test matrix

A UAT test matrix is a table that organises scenarios and combines conditions to cut the number of tests you need. You can break scenarios into hierarchies, such as “new customer” and “existing customer”, and vary conditions across the matrix. The goal is to cover the scenarios that are most likely, most critical and most error-prone. It will not cover every combination, so test planning matters. Test management tools such as PractiTest let you reuse tests from a test library across different test sets.

How to write acceptance criteria

Acceptance criteria say exactly when a requirement is considered done. A common format is Given, When, Then:

  • Given a registered customer with items in the basket,
  • When they pay with a valid card,
  • Then the order is confirmed, a confirmation email is sent and the stock level is reduced.

Good criteria are specific, testable and written in business language. For more worked cases, see the guide to user acceptance criteria with UAT examples.

UAT test case example

ID Scenario Steps Expected result
UAT-01 Customer places an order Sign in, add an item, pay by card Order confirmed and email received
UAT-02 Payment declined Pay with a card that is declined Clear error message and basket kept
UAT-03 Support agent refunds an order Open the order, choose refund Refund recorded and customer notified

A ready-made structure for plans, scripts and sign-off is in the UAT template.

UAT exit criteria and sign-off

UAT ends when the agreed criteria are met. Typical exit criteria are:

  • All critical business scenarios have been executed.
  • No open severity 1 or 2 defects, and agreed handling for lower-severity ones.
  • The required percentage of test cases has passed.
  • Business owners have signed off in writing.
  • Known issues and workarounds are documented.

Use the UAT checklist to confirm nothing is missed.

UAT test environment and data

Decide early whether the UAT environment will become the live production environment, which can ease the move to go-live. Otherwise, keep a dedicated environment that mirrors production. Test data should never be an exact copy of production data. Production data contains sensitive personal information, so using it risks privacy breaches. It can also trigger emails and notifications to real customers. Use sanitised or synthetic data that keeps the structure and behaviour of real data without exposing anyone.

Tools used in UAT

  • Test management tools: plan, schedule and track test cases and results.
  • Test data creation and management tools: produce realistic, safe data sets.
  • Defect tracking tools: log, prioritise and follow defects through to closure.

Test automation can help with repeated work in UAT, such as regression, performance and security checks, but it needs good tools that integrate with test management, data and defect systems, plus technical skill to set up. For user evaluation of workflows, manual testing by real users remains the core of UAT.

UAT in agile projects

In agile teams, UAT often happens every sprint: the product owner and users review and accept each story against its acceptance criteria, then a final release-level UAT confirms the whole product. Keep stories small and acceptance criteria clear so acceptance is quick.

Common UAT mistakes

  • Starting too late, so there is no time to fix what UAT finds.
  • Using the wrong testers, such as people who do not know the business process.
  • Unclear acceptance criteria, which leads to arguments about whether something passes.
  • Using production data in the test environment.
  • Treating UAT as a repeat of system testing instead of a business-focused check.
  • No defect triage, so every report becomes a blocker or none does.
  • Entering UAT with unstable software, which wastes users’ limited time.

UAT FAQ

How is user acceptance testing done?

End users or representatives run predefined test cases and realistic scenarios against the software and record the results. Test engineers may design the cases while users execute them.

How long does UAT take?

It depends on the size and complexity of the application. It can take a few days for a small change and several weeks for a large system.

When is UAT done?

In the later stages of the lifecycle, after system integration testing and before deployment. Severity 1 and 2 defects from integration testing should be fixed before UAT starts.

Who is responsible for UAT?

Business stakeholders and end users are responsible for executing the tests and accepting or rejecting the software, with a coordinator organising the work.

How do you write UAT test cases and scripts?

Base them on user requirements and real workflows. Write step-by-step actions, input data and expected results, and cover both positive and negative scenarios.

Are UAT testers paid?

Business users who take part in UAT are normally not paid separately, because it is part of their job. If you recruit external testers or outsource UAT, rates depend on region and experience.

Is UAT a verification activity?

No. Verification checks whether the system is built correctly against specifications through reviews, inspections and static analysis. UAT is validation: it checks the system against the user’s real needs.

Can UAT be automated?

Partly. Repetitive checks such as regression can be automated with the right tools and skills, but user judgment about workflows and usability still needs people.

What is the difference between UAT and QA testing?

QA and system testing verify the software against specifications. UAT is done by users to validate it against business needs.

What happens if UAT fails?

The team logs the defects, fixes the blocking ones, retests and runs another cycle. Release waits until the exit criteria are met or the business explicitly accepts the risk.

Want more testing guides in your Google results? Add Testmetry as a preferred source.

Share it :

Leave a Reply