UAT Templates

This page gives you simple, beginner‑friendly templates for writing UAT test cases, defect logs, scenarios, and acceptance criteria. Each template includes a filled‑out example and a blank version you can copy and paste into your own UAT documentation.

UAT Test Case Template

A UAT test case is the step‑by‑step script a tester follows to confirm a requirement works correctly.

Test Case Template (Beginner‑Friendly)

  • Test Case ID: Unique number for this test
  • Requirement: What requirement this test is validating
  • Scenario: Short description of what the user is trying to do
  • Pre‑Conditions: What must be true before testing begins
  • Test Steps:
  • Expected Result: What should happen if the system works
  • Actual Result: What actually happened during testing
  • Pass/Fail: Did the test pass?
  • Defects (if any): List any issues found

Filled‑Out Example (Address Update)

  • Test Case ID: TC‑001
  • Requirement: Customer must be able to update their mailing address.
  • Scenario: Update address successfully.
  • Pre‑Conditions: Customer is logged in and has an existing profile.

Test Steps:

  1. Go to “Profile” → “Mailing Address.”
  2. Enter a new valid address.
  3. Click “Save.”
  4. Confirm the new address appears on the profile page.
  • Expected Result: New address is saved and displayed correctly.
  • Actual Result: New address appears correctly.
  • Pass/Fail: Pass
  • Defects: None

Blank Version (Copy & Paste)

  • Test Case ID:
  • Requirement:
  • Scenario:
  • Pre‑Conditions:

Test Steps:

  • Expected Result:
  • Actual Result:
  • Pass/Fail:
  • Defects (if any):

UAT Defect Log Template

A UAT defect log is where testers record issues found during testing so developers can reproduce and fix them.

Defect Log Template (Beginner‑Friendly)

  • Defect ID: Unique number for this defect
  • Issue Summary: Short description of the problem
  • Severity: Low, Medium, High, Critical
  • Status: Open, In Progress, Fixed, Closed
  • Steps to Reproduce:
  • Actual Result: What happened during testing
  • Expected Result: What should have happened
  • Assigned To: Developer or team responsible
  • Comments: Any extra notes

Filled‑Out Example (Address Validation Error)

  • Defect ID: D‑101
  • Issue Summary: Address field does not validate correctly
  • Severity: High
  • Status: Open

Steps to Reproduce:

  1. Go to “Profile” → “Mailing Address.”
  2. Enter an invalid address (e.g., “123”).
  3. Click “Save.”
  • Actual Result: Error message appears: “Invalid address format.”
  • Expected Result: Address should be accepted only if valid; error should be clear and helpful.
  • Assigned To: Sarah
  • Comments: Occurs only on Chrome.

Blank Version (Copy & Paste)

  • Defect ID:
  • Issue Summary:
  • Severity:
  • Status:

Steps to Reproduce:

  • Actual Result:
  • Expected Result:
  • Assigned To:
  • Comments:

UAT Scenario Template

A UAT scenario describes a real‑world action a user performs in the system.

Scenario Template (Beginner‑Friendly)

  • Scenario ID: Unique number for this scenario
  • Scenario Name: Short title describing the user action
  • Business Process: Which business workflow this scenario belongs to
  • Pre‑Conditions: What must be true before the scenario begins
  • User Action: What the user is trying to accomplish
  • Expected Outcome: What should happen if the system works correctly
  • Notes: Any additional details or assumptions

Filled‑Out Example (Update Mailing Address)

  • Scenario ID: S‑001
  • Scenario Name: Update Mailing Address
  • Business Process: Customer Profile Management

Pre‑Conditions:

  • Customer is logged in
  • Customer has an existing profile
  • User Action: Customer updates their mailing address in the profile section

Expected Outcome:

  • New address is saved
  • Updated address displays correctly on the profile page

Notes:

  • Address validation rules must be applied
  • Scenario supports both domestic and international addresses

Blank Version (Copy & Paste)

  • Scenario ID:
  • Scenario Name:
  • Business Process:
  • Pre‑Conditions:
  • User Action:
  • Expected Outcome:
  • Notes:

UAT Acceptance Criteria Template

Acceptance criteria define what must be true for a requirement to be considered complete.

Acceptance Criteria Template (Beginner‑Friendly)

  • Criteria ID: Unique number for this acceptance criterion
  • Requirement: The requirement this criterion belongs to
  • Description: Clear statement of what must be true
  • Pre‑Conditions: Anything that must exist before validation
  • Acceptance Steps:
  • Expected Outcome: What should happen if the criterion is met
  • Notes: Any assumptions or clarifications

Filled‑Out Example (Address Update Requirement)

  • Criteria ID: AC‑001
  • Requirement: Customer must be able to update their mailing address
  • Description: The system must save and display the updated mailing address

Pre‑Conditions:

  • Customer is logged in
  • Customer has an existing profile

Acceptance Steps:

  1. Navigate to “Profile” → “Mailing Address.”
  2. Enter a valid new address.
  3. Click “Save.”

Expected Outcome:

  • Address is saved
  • Updated address appears correctly on the profile page

Notes:

  • Address validation rules must be applied
  • Error messages must be clear if the address is invalid

Blank Version (Copy & Paste)

  • Criteria ID:
  • Requirement:
  • Description:
  • Pre‑Conditions:

Acceptance Steps:

  • Expected Outcome:
  • Notes:

What You Should Do Next

Now that you have the templates, your next step is to start practicing with real UAT exercises.