UAT Test Cases


Phase: Monitoring and controlling | Audience: Shared | Project: WEB-2026-01 Corporate Website Development


Understand it first

In simple words: UAT (User Acceptance Testing) Test Cases are real business scenarios the client runs to decide whether the website works well enough to accept.

Think of it like: Before buying a car, you test drive it: start it, reverse, check brakes, try the music system. Each check is a test case.

When is it created?

Prepared before UAT (20 Nov 2026), run 1–4 Dec

Who prepares it?

QA Tester prepares

Who approves or uses it?

Client testers run them

What happens next?

Results lead to the UAT Sign-off Form


How it connects to other documents

  1. Scenarios come from the RFP requirements and Scope Statement.
  2. Rules come from the Quality and Test Plan.
  3. Includes CR-001 (Careers page) from the Change Log.


The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Business scenarios the client will run between 1 and 4 Dec 2026 to decide whether to accept the website.

Item


Detail


Document no.

WEB-2026-01/UTC

Version

1.0

Date

20 Nov 2026

Owner

QA Tester

Audience

Shared with client

Phase

Monitoring and controlling


1. How to use this script

  1. Use the staging link shared by the PM.
  2. Run each case on a phone and on a laptop.
  3. Mark Pass or Fail; for Fail, describe what happened and attach a screenshot.
  4. Send the completed sheet to the PM each evening.


2. Test cases

ID


Area


Steps


Expected result


Priority


Result


UAT-01

Home

Open the home page on a phone

Page loads in under 3 s; layout fits the screen

Must


UAT-02

Navigation

Open the menu on a phone and visit each page

All menu links work

Must


UAT-03

Services

Open each of the 4 services pages

Correct content and enquiry button

Must


UAT-04

Portfolio

Filter projects by category

Only matching projects shown

Should


UAT-05

Blog

Open blog listing and go to page 2

Posts listed newest first; pagination works

Should


UAT-06

Blog

Open a blog post

Title, date, image and related posts shown

Should


UAT-07

Contact form

Submit the form with valid details

Thank-you message; email reaches sales inbox within 1 minute

Must


UAT-08

Contact form

Submit with an invalid email address

Clear error message; form not sent

Must


UAT-09

Careers (CR-001)

Open Careers and click Apply

Opens email to HR with job title in subject

Must


UAT-10

CMS

Log in and change text on About Us

Change appears on the live page after publishing

Must


UAT-11

CMS

Create and publish a blog post with an image

Post appears at top of blog listing

Must


UAT-12

CMS

Add a new job on Careers

Job appears on Careers page

Must


UAT-13

SEO

View page title in the browser tab for each page

Each page has a unique, meaningful title

Should


UAT-14

Analytics

Visit the site and check GA4 real-time report

Visit is recorded

Must


UAT-15

Security

Open the site with http://

Redirects to https:// with padlock

Must



WEB-2026-01/UTC · v1.0 · Shared with client. Bracketed items such as [Client Name] are placeholders.


Key takeaways

  1. Write steps in simple language a non-technical client can follow.
  2. Mark priority: Must-pass cases decide acceptance.
  3. Test on both phone and laptop.


Common mistakes to avoid

  1. Writing technical test cases the client cannot run.
  2. Missing approved change requests.
  3. No clear expected result.


Next lesson: 34. UAT Sign-off Form