Company logo here
Company name here
Unit Test Scripts
Authority: R12 SRT
TS-R12.0000
Initial Issue Date
2.9.2012
Revision Date:
2.9.2012
Revision No.
Guidelines for Developing Test Scripts
Preparation: initials
Doc No:
1.2
Next Revision Date:
Issuing Dept: IS
Page:
Page 1 of 3
Contents
General.......................................................................................................................................................... 2
Script Header ................................................................................................................................................ 2
Table of Contents .......................................................................................................................................... 2
Scenario Headings ......................................................................................................................................... 2
Navigation Heading ................................................................................................................................... 2
Scenario Heading ...................................................................................................................................... 2
Creating Scenarios ........................................................................................................................................ 3
Step Column .............................................................................................................................................. 3
Test Column .............................................................................................................................................. 3
Actions Column ......................................................................................................................................... 3
General.................................................................................................................................................. 3
Actions .................................................................................................................................................. 3
Data ....................................................................................................................................................... 3
Uncontrolled copy if printed.
Valid on day of printing only.
Printed on: 19 May 2013 9:31 AM
Your company name here.
General
Scripts are defined by a specific responsibility that a user will be using.
There is one and only one script per responsibility.
Script Header
The responsibility name goes in the heading on the first page in the box just below the logo.
The person preparing the script should put their initials in the Preparation box.
Nothing else needs to be filled on the header
Table of Contents
This will be generated automatically based on the headings in the script
To update the table of contents, click in it and then click on Update Table on the tab that pops up on
the top left.
Scenario Headings
Navigation Heading
Navigation is the first heading and uses the Heading 1 style. There can/will be multiple Navigation
headings per script. The format for the navigation description is:
o Navigation: Transactions > Receiving > Receipts.
o It uses a greater than sign (>) to indicate when the tree needs to be expanded
o The final item in the list is the form that will open when the user clicks on it
Scenario Heading
The second heading is Scenario. It uses the Heading 2 style. There can be multiple scenarios within a
single navigation path. The basic format is:
o Scenario 1: Create a General Ledger Journal Batch
o It starts with the number of the Scenario under a particular navigation path, followed by a
description of the function that the user is going to be performing
o If there are other scenarios that the user can perform using the same navigation, then all
the scenarios should be included. As an example, if we are in an Order Management User
responsibility and the navigation is Orders, Returns > Order Organizer, then all the things a
user can do under that path should be scenarios under that path. Scenarios would include
things like, Create New Hardware Order, Create New Systems Order, Find an Existing order
by Order Number, Find all orders for a customer, Cancel an order
Uncontrolled copy if printed.
Valid on day of printing only.
Printed on: 19 May 2013 9:31 AM
Your company name here.
Creating Scenarios
Step Column
Steps use a 1.1 format. The first number is the number of the scenario. The second number (after
the dot) is the number of the test step for this scenario. It will always start with 1 and will increment
by 1 with each step. As an example:
o Scenario 1 could have steps 1.1, 1.2, and 1.3. Scenario 2 could have steps 2.1, 2.2, 2.3.
Test Column
Test is a brief description of the test step that the user is being asked to perform.
Actions Column
General
The actions section consists of a combination of Actions and Data.
Actions
Actions are bullets. Examples of actions are:
o Clink Button
o Save
o Enter Data
o Instructions like Review batch before posting
Special formatting within an Action
o Putting a box around a Button and shading it blue.
o Using underlines and the greater than sign (>) to indicate menu elections. An example would
be View > Record > Last
o Enter Data is a special type of action that has a table inserted immediately below it.
Data
Data is entered into a two column table just below the Enter Data action
The column on the left should contain the field label or column heading where the data is being
labeled
The column on the right will contain the value that needs to be entered. The value will be in bold.
If there is default data already in the field, it is Ok to just enter Use default into the value column
If there are entity specific requirements for entering data like batch numbers, it is Ok to put Use
entity standard in the value field. We want the test to be as close to real life as we can make them.
Data should be entered in tab sequence order. So, start with the first field and add it to the table.
Tab to the next field and add it to the table. Tab to the next field and add it to the table
Fields that do not need values and are left blank should not be added to the table.
Uncontrolled copy if printed.
Valid on day of printing only.
Printed on: 19 May 2013 9:31 AM
Your company name here.
