XXX < the system name> System Test Script Document

XXX <the name of the use case or part of the system requirement that is tested by the test script>
<Template instructions: Text in this style should be removed. Text in Normal style should be replaced. After using the template for some time you
might remove some of the sections if they are unused, or adapt it more closely to suit the general style in use within your company. Copyright in
this template remains with CRaG Systems>
<This template should be modified by the test developer to provide the test script. The resulting test script is then printed or copied once for each
time the test is to be run. The tester completes the script with actual results>
<The tester completes the following information about when the test script was actually run and the overall summary result>
Date Run

Time Run

Tester

Pass/Fail (P/F)

Summary of Failure

Assumptions:
1. xxxx <include here all assumptions that the test makes about the system. For example: the system hardware is functioning correctly >
2. xxxx <further assumptions>
System Requirements Covered:
1. xxxx <include here a reference to each system requirement or set of requirements that is covered by this test script>
2. xxxx <further requirements covered >
Exclusions:
1. xxx <include here anything that it is not obvious that the test script does not test for >
2. xxx <further exclusions>
Setup:
1. xxx <list all the required steps that should be completed before executing this script. Optionally this could be described as a set of preconditions.>
2. xxx <further steps>
User Action

Value(s) Entered

Expected Result

Pass/Fail/Untested (P/F/U)

<you can choose

whether to
predefine these or
allow the tester to

<describe how the system is normally expected to

respond>

<if the system responds

incorrectly then the tester
should include a short
description of the fault >

xxxx xxx xxxxx <describe what the

tester should do to the system >

Author: <the authors name>

Page 1 of 2

Printed: 23/04/2003 15:03

XXX < the system name> System Test Script Document

XXX <the name of the use case or part of the system requirement that is tested by the test script>
decide>
2

xxxx xxx xxxxx <further lines as

described above >

Teardown:
1. xxxx <include here all the steps that should be taken after the test script has been executed>
2. xxxx <further steps>
Outstanding Issues:
1. xxxx <include here any issues associated with incompleteness, ambiguity or difficulty in understanding the supplied specification artefacts or
with the testability of the system>
2. xxxx <further issues>

Author: <the authors name>

Page 2 of 2

Printed: 23/04/2003 15:03