Skip to tutorial content
Rate module Not yet rated

UAT Test Scripts with Process Owners

4 min read
On this page

In this lesson, you will learn:

  • What a UAT script is
  • The parts of a good script
  • SNWR’s major incident script
  • How to run it with Daniel

🔁 Quick look back: Last time: Test Strategy for an ITSM Rollout. You learned SNWR’s four kinds of testing, and who tests what on which instance.

1 “Just have a play with it”

Daniel is asked to “test the major incident process”.

  • He clicks around for 20 minutes.
  • He says it “looks fine”.
  • Nobody knows what he checked.

🎯 The problem: Testing without a script is guessing. You can’t repeat it or prove it.

👉 The fix: write a script with steps and expected results, and run it together.

2 A UAT script

Key term: UAT script

A list of steps for a real scenario, each with what should happen.

Key term: Expected result

What should happen after a step. If it doesn’t, it’s a defect.

UAT script: Major incident from proposal to review. Tester: Daniel Okafor on snwrtest. Step 1: As Abel, propose INC0010150 as a major incident. Expected: state Proposed, Daniel notified. Step 2: As Daniel, accept it. Expected: major incident state Accepted, communication plan starts. Step 3: Add a child incident. Expected: it shows in the child list. Step 4: Resolve the parent. Expected: children resolve too. Step 5: Complete the post-incident review. Expected: a problem is created.
Figure 1. Every step has an expected result.

3 Running it

  1. Book an hour with Daniel on snwrtest.
  2. He does the steps. You watch and take notes.
  3. For each step, mark Pass or Fail.
  4. Log each Fail as a defect, with a screenshot.
  5. When all steps pass, Daniel signs off.

💡 Good to know: Use real SNWR names and records. Daniel will spot things a made-up example would hide.

4 Let’s try it: write and run a UAT script

  1. Copy the five steps above into a document or a test management tool.
  2. Add a column for Pass/Fail and a column for notes.
  3. On your instance, run each step yourself as Abel and Daniel (impersonate).
  4. Mark each step. Log any Fail as a defect with steps to repeat it.
  5. Add a sign-off line: tester, date, result.

5 Quick recap

  • A UAT script lists steps for a real scenario
  • Each step has an expected result
  • Process owners run it; you watch
  • Every Fail becomes a defect
  • Daniel signs off when all steps pass

6 Check yourself

Think of your answer first. Then tap to check.

1 What makes a step pass? Show answer

The expected result happens.

2 Who runs the major incident UAT script? Show answer

Daniel, the process owner.

3 A step fails. What do you do? Show answer

Log a defect, with steps and a screenshot.

4 Why use real SNWR names? Show answer

Process owners spot problems a made-up example would hide.

Nice work! You can run UAT with a process owner. 🎉
Next up: An ITSM Regression Pack with ATF

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.