Sogeti Nederland B.V. 1.0 1
May 9th, 2008
TEST SCRIPT <OPTIONAL: NAME TEST SCRIPT>
<<In this template (blue) text stands in between << and >> (<<text>>). The text
contains sample text, comments or explanations and should be deleted or replaced by
final text. Depending on need all other standard text can be removed.
N.B.: The final form and content of the test script is organization and sometimes
project specific. This way of documentation is one of the possibilities in MS Word.
Depending on the situation documentation in a spreadsheet can be a good alternative.
For that situation templates are available also. >>
1.2 Preparation of the initial situation
Before this test script can be executed the following actions should be taken to create
the desired initial situation:
<<Actions to be taken before start such as:
- Refresh the database and build a database with “real” functions or
- Load a certain database (for example reference to a certain back )
- Configure the desired system for exact date and so on>>
1.3 Actions and controls
- At 'Id': reference here to the test cases.
Commonly used conventions are:
- ff-aa, where 'ff' is the number of the test case and 'aa' the number of the test
case to be executed. For one test case it can be necessary to execute several
actions. When the number of test cases grows ‘aa’ starts with 01;
- nn-ff-aa: the same as above but with 'nn' to indicate the number within this test
script (is always increasing starting with 01);
- if one wants to describe a ‘initial situation’ one can describe a first action at the test
case. Otherwise one can use step 1.2 if this applies to the whole test script;
- At ‘Pass/Fail': ‘Pass’ can be marked with a check or a ‘P’, ‘Fail’ can be marked with
an X or an ‘F’. Defects numbers are stored in the Remarks section. You can use the
column “Remarks” for additional statements or observations. >>