Welcome & What This Page Covers

This page shows you real, beginner‑friendly examples of UAT so you can see how everything fits together in practice.

You’ll see:

  • A simple business requirement
  • The test scenarios and test cases created from it
  • The defects found during testing
  • How the business decided whether to accept or reject the change

The goal is simple:

Help you understand UAT by seeing it in action.

Example 1: Customer Address Update

Business context: A bank wants customers to be able to update their mailing address online instead of calling support.

Requirement (plain language): “Customers must be able to log in, update their mailing address, and see the new address reflected on their profile and in future statements.”

Test Scenarios & Test Cases (Example 1)

Test Scenario 1: Update Address Successfully

  • Log in as an existing customer
  • Go to “Profile” → “Mailing Address”
  • Enter a new valid address
  • Save the change
  • Confirm the new address appears on the profile page
  • Confirm the old address is no longer shown

Test Scenario 2: Handle Invalid Address

  • Log in as an existing customer
  • Go to “Mailing Address”
  • Enter an incomplete address (missing city or ZIP)
  • Try to save
  • Confirm an error message appears
  • Confirm the address is not updated

Test Scenario 3: Security & Access

  • Try to access the address update page without logging in
  • Confirm you are redirected to the login page
  • Confirm no customer data is visible

Defects Found in UAT (Example 1)

Defect 1: Old address still appears on statements

  • Profile shows the new address
  • Next generated statement still shows the old address
  • Impact: customers may receive mail at the wrong address

Defect 2: No error message for incomplete address

  • System allows save when city is missing
  • Creates bad data in the system
  • Impact: downstream processes (mailing, compliance) may fail

UAT Decision (Example 1)

Because the address did not update correctly in all places and invalid data was allowed, the business did not accept the change.

The team fixed the defects, retested, and only then gave UAT acceptance so the feature could go live.

Example 2: Loan Application Status

Business context: A customer applies for a loan online and wants to check the status.

Requirement (plain language): “Customers must be able to view the current status of their loan application on the dashboard.”

Test Scenario 1: View loan status

  • Log in
  • Go to dashboard
  • Confirm loan status appears correctly

Test Scenario 2: No loan application

  • Log in as a customer with no loan
  • Confirm dashboard shows “No active applications”

Defect found: Status shows “Pending” even after approval → business rejects the change until fixed.

What You Should Do Next

Now that you’ve seen real UAT examples, your next step is to start working with templates and practice exercises.

You’ll get:

  • UAT test case templates
  • Defect log templates
  • Scenario templates
  • Practice exercises to build confidence

Move on to:
UAT Templates
Practice Exercises