User acceptance testing for websites
User acceptance testing (UAT) is the phase in which the client checks that the website does what was agreed, before it goes live. Done well, it ends with a clear sign-off. Done badly, it turns into weeks of scattered feedback. Here is how to run it well.
What is user acceptance testing?
User acceptance testing is the last test phase of a website project. The client, or people chosen by the client, use the finished website on a staging environment and confirm that it meets the agreed requirements. The result is either a list of findings to fix or a formal acceptance.
UAT is not a second design review. Changes to agreed designs or new wishes are recorded as change requests, not as UAT findings.
Prepare
- A staging website with realistic content and data, as close to the live setup as possible
- Test scenarios based on the agreed requirements, for example "a visitor books a table for four people tomorrow evening"
- The list of testers on the client side, their devices, and the dates of the test rounds
- One agreed channel for findings and a short explanation of how to report
- Definitions of severity, for example blocking, major and minor
Run the test rounds
- Hold a short kick-off. Show the staging website, the scenarios and how to report a finding.
- Testers work through the scenarios and report each finding separately, on the page where it happens.
- Your team triages findings daily: bug, change request or not reproducible. Ask questions in the finding itself.
- Fix the agreed findings and mark them for retest. The reporter checks and confirms.
- Repeat for a second round if needed. Two rounds are usually enough.
Get the sign-off
Acceptance is easier when the criteria are clear from the start. A common rule is that the website is accepted when there are no open blocking or major findings; minor findings are fixed after launch within an agreed time. Record the acceptance in writing with the date and the list of open minor items.
Typical pitfalls
- Testing on the wrong environment, or on staging with empty content
- Feedback without page, device or steps, which leads to "cannot reproduce"
- Change requests mixed into the findings, which blurs the scope
- No end date for the rounds, so testing never ends
Tools for UAT
A visual feedback tool makes UAT faster for both sides. In mumus, client testers are free guests. They click on the problem on the staging website, the screenshot, page and browser are attached, and each finding lands on a board where your team prioritises, fixes and hands it back for retest. Clients see the status of their findings at any time.
Frequently asked questions
Who performs user acceptance testing on a website?
The client or end users chosen by the client. The agency or development team prepares the staging website and the test scenarios, explains how to report findings and fixes them, but does not accept its own work.
How long should UAT for a website take?
For a typical company website, one or two rounds of about a week each are common. Agree the dates and the acceptance criteria before testing starts.