User Acceptance Testing Report (UAT)
The result of a user acceptance test: scope and environment, every test case with its outcome, the pass rate and defect counts worked out for you, the sign-off decision and the signatures.
Free. Fill in, print, save as PDF or download as Word without an account. Saving to your account needs a free account.
Country versions
- International
A template, not advice.
Read more
What it is
User acceptance testing (UAT) is the last check before a system goes live: the people who will use it, or who speak for the business, try it against real scenarios and say whether it does the job. This report is the record of that test. It states what was tested and in which environment, lists every test case with its expected and actual result, counts the outcomes and the defects, and ends with the decision of the business owner.
The form counts passed, failed, blocked and not-run cases for you and works out the pass rate (passed cases as a share of the cases that were run), which it compares with the target you set before the test. The defect table is counted by severity and by status, and the number of open critical or major defects is shown on its own, because a go-live decision usually turns on it. The decision is a tick (accepted for release, accepted with conditions, not accepted) with three signatures. There is one international version. The report is a record of a test, not legal advice.
When to use it
- A system, release or change is about to go live and the business has to say whether it is ready.
- A client or sponsor asks for written evidence of what was tested and what failed.
- You need a compact record that the tester, the test lead and the business owner can all sign.
- Payment, a milestone or a go-live depends on documented acceptance testing.
How to fill it in
- Enter the project, the release and build, the test period and the environment; name the test lead, the business owner and the testers.
- Write what is in and out of scope and the acceptance criteria before testing starts, and set the pass-rate target.
- List the test cases with scenario and expected result and, after running them, the actual result and outcome; link each failure to a defect.
- List the defects with severity and status; the counts by severity and status and the open critical or major defects are worked out.
- Read the results: pass rate, share of cases run and the check against the criteria.
- Tick the decision, write any conditions and have the three roles sign.
Common mistakes
- Setting the criteria after the results are in. A target chosen afterwards judges nothing.
- Counting blocked cases as passed. A case that could not be run proves nothing; list it as blocked and say why.
- Vague expected results ("works well"). A tester cannot pass or fail a case without a concrete expected result.
- Mixing up severity and priority. Severity says how serious a defect is; priority says how soon it will be fixed.
- Signing without the retest. If a defect is fixed after the test, record the retest before the final sign-off.
Steps at a glance
- Fill in
- Check the preview
- Save as PDF, Word or Excel
Country versions
Pick the country you need. Each version uses the wording and layout commonly found there; a version marked “check with local advice” should be read by someone who knows the local rules before it is used.
- International (XX): Written in English, Korean, Japanese, German
Designs
The same form in several designs. The fields and the wording stay the same; only the look changes.
- Ledger
- Banner
- Executive
- Classic
- Modern
- Formal
- Minimal
- Side band
- Compact
- Boxed form
- Warm
- Plain (black and white)
Your details fill it in
Fields that ask for your name, address or company details are filled from My details, so you do not type them again; you can still change any field for one form. Signed in, your details stay in your account; otherwise they stay in this browser only. A passport, identity or social security number is never saved.
Questions
- How is the pass rate calculated?
- Passed cases divided by passed plus failed cases, in percent. Blocked and not-run cases are counted separately, so they neither raise nor lower the rate; the "cases run" figure shows how much of the plan was covered.
- What is the difference between severity and priority?
- Severity says how serious the effect of a defect is: critical, major, minor or trivial. Priority says how soon it should be fixed. This report records severity; mention priority in the decision text if it matters.
- Who should take part in the test?
- People who know the business process and will use the system, not only developers. The test lead organises the test and the report; the business owner decides whether the result is accepted.
- What does the check against the criteria mean?
- The form compares the pass rate with your target and checks that no critical or major defect is open. It is an aid for the decision, not the decision itself; the business owner decides.
- Can I use it for the test of a single feature?
- Yes. Use a short list of cases; the report works the same for a handful of cases or a few hundred.
- Is this form legal, tax or accounting advice?
- No. It is a template: it gives you the usual structure and wording, not advice. Rules differ by country and case, so have someone qualified read anything that matters before you sign, send or file it.
- Which countries and designs does it come in?
- It comes in 1 country versions: International. 12 designs.
A form is a template, not legal, tax or accounting advice. Rules differ by country and case.