0% found this document useful (0 votes)
126 views7 pages

EVO35 - UAT Test Script Details Template

This document provides a test script for user acceptance testing (UAT) of a new customer creation process. The 3-sentence summary is: The test script details the steps to create a new customer in the accounts receivable module, including entering customer name, group, and additional details. It outlines the expected result of successful customer creation and provides space to record the actual results. Upon completion, the tester and approver will sign off to verify if the test passed or failed.

Uploaded by

Dickson Allela
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
126 views7 pages

EVO35 - UAT Test Script Details Template

This document provides a test script for user acceptance testing (UAT) of a new customer creation process. The 3-sentence summary is: The test script details the steps to create a new customer in the accounts receivable module, including entering customer name, group, and additional details. It outlines the expected result of successful customer creation and provides space to record the actual results. Upon completion, the tester and approver will sign off to verify if the test passed or failed.

Uploaded by

Dickson Allela
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

UAT Test Script

Prepared for

[Customer Name]

Project

[Project Name]

Prepared by

[Consultant Name]

Contributors
[Document contributors]

Revision and Signoff Sheet


Change Record
Date

Author

Version Change reference

Client Review
Name

Version approved

Position

Date

Table of Contents
Contents
UAT Test Script ......................................................................................................................................... 1
Change Record .......................................................................................................................................... 1
Table of Contents ...................................................................................................................................... 1
1

Script Details ...................................................................................................................................... 2

Test Script ........................................................................................................................................... 3


[Script Number] [Script Name] ................................................................................................................... 3

Results Information ............................................................................................................................ 5

1 Script Details
Script number

[Enter Script Number]

Functional Domain

[Enter Functional Domain]


e.g. Finance

Role

AR Clerk or AR Manager

Script name

[Script Name]
e.g. Create a Customer

Purpose

[Enter Script Purpose]


e.g. To create a new customer

Environment

[Enter Test Environment and/or Company Name]

Data requirements

[What Data is Required to Test?]


e.g. Customer groups, terms of payment, method of payment, address format,
zip/postal codes, number sequences

Dependencies

[Enter any Dependencies or None]

Scenario

[Enter the script scenario]


e.g. Setup a new customer and validate that the appropriate values populate a
newly created order

2 Test Script
[Script Number] [Script Name]
Accounts Receivable Maintenance Customers Add
Step 1: [Enter the details for the first step in the script. The level of step-by-step detail for the script will
depend on the functional and system knowledge of the consultant(s) or user(s) performing the scripted
testing. Incorporating tables with the usage data (e.g. field, value to be entered/selected, comments) can
greatly assist the testing resources:
e.g.
Field

Value

Comments

Customer

Will default

Enter a name for the customer. If you use automatic


account number generation, the system uses the first
letters of the customer name in the account number field.

Name

Home Design Gallery

Customer Group

20

Retail stores

Step 2: Click OK and then Edit to add additional details if required.

3 Results Information
Expected Results
[Enter the details of what results are expected from the test and what criteria will define the test results
as successful]
e.g.
Customer should get created in Accounts Receivable module
Achieved Results/Comments
[Enter the details of the actual results of the test, including any screenshots of the system (e.g. error
messages) if beneficial for further tests or troubleshooting.]

Pass

Fail

Tested by: [Tester Name]

Completion Date: [Insert Date]

Approved by: [Approver Name]

Completion Date: [Insert Date]

You might also like