0% found this document useful (0 votes)
277 views3 pages

UAT Script Template v1

This document provides a template for a user acceptance test (UAT) script. It includes sections for test phase and ID, business area and scenario description, purpose, dependencies, date written and executed, data set-up, and test steps with expected results. The test steps section lists the specific actions to be tested and expected outcomes to verify the purpose of the scenario.

Uploaded by

Adedapo Sodipo
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
277 views3 pages

UAT Script Template v1

This document provides a template for a user acceptance test (UAT) script. It includes sections for test phase and ID, business area and scenario description, purpose, dependencies, date written and executed, data set-up, and test steps with expected results. The test steps section lists the specific actions to be tested and expected outcomes to verify the purpose of the scenario.

Uploaded by

Adedapo Sodipo
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

63761907.

doc

Template UAT Test Script


SUMMARY
TEST PHASE: TEST ID: BUSINESS AREA: SCENARIO DESCRIPTION: PURPOSE:

UAT

(UAT=USER ACCEPTANCE TEST, ST=SYSTEM TEST) VERSION:

e.g. CMUAT5.2 Business area or system being tested

1.0

RUN NUMBER:

01

A meaningful description of what is being tested by this script. May refer back to Use Case scenarios. Details of any specific conditions to be tested by this script (this section may be removed as there is some overlap with Scenario Description).

DEPENDENT ON:

What scripts need to be run What scripts need to be run

prior to this one

DEPENDENT FOR:

after this one

DATE WRITTEN BY: EXECUTED BY: SIGNED OFF BY:

NAME

SIGNATURE

FINAL STATUS:

(P=PASSED, F=FAILED, S=SCRIPT RE-WRITE, D=DATA UNAVAILABLE, X=ON HOLD)

1 of 3

63761907.doc

DATA SET-UP
ENTITY NAME DETAILS

Entity or Table name

Details of tables or entities that need to exist before this script can be run. These may either be set-up in a previous script or will need to be created before execution of the script.

2 of 3

63761907.doc

TEST STEPS
STEP ACTIONS EXPECTED RESULTS COMMENT PASS/FAIL

1.

Precise instruction for what the tester should do.

What the system should do in response. There may be more than one expected result per Action

Filled in by hand during test execution

Filled in by hand during execution

2. 3.

4.

5.

6.
7.

8.

3 of 3

You might also like