Sie sind auf Seite 1von 9

Agile Test Script Template

Introduction
The following pages of this document contain a Test Script template that may be copied and
used within your own testing task or project.
The Test Script template contains the following sections:
Project ID - the uniue project identifier
!"T #ame - the definiti$e name of the !pplication "nder Test %front sheet
only&
!"T 'ersion - the definiti$e $ersion information for the !pplication "nder
Test %front sheet only&
Iteration ID - the uniue identifier for the iteration this test is being conducted
in %front sheet only&
Date of Test - the planned start date of testing %front sheet only&
Test ID - the uniue identifier for the test
Purpose of Test - a brief description of the purpose of the test including a
reference where appropriate to the reuirement that is to be tested %consider pro$iding
references to the reuirements specification( design specification( user guide( operations
guide and)or installation guide&( as well as any dependencies from or to other Test
Scripts)Test *ases
Test +n$ironment - a brief description of the en$ironment under which the test
is to be conducted %may include a description of the state of the !"T at the start of this
test( details regarding the platform or operating system( as well as specific information
about data used in this test&
Test Steps - concise( accurate and unambiguous instructions describing the
precise steps the Tester must take to e,ecute the test( including na$igation through the
!"T as well as any inputs and outputs
+,pected -esult - a brief and unambiguous description of the e,pected result
of e,ecuting the test.
.here te,t appears in angle brackets %/ 0&( this denotes a place marker( which must be
replaced with the appropriate information for a particular testing phase. 1or e,ample
/*lient0 should be replaced by the name of your own company or organisation.
1igure 2 below pro$ides an e,ample of how the Test Script template pro$ided in this
appendi, might be completed in practice.
<Client> Test Script %front sheet&
Project ID
AUT Name Version
Iteration ID Date of Test
Test ID
Purpose of Test
Test Enironment
Test Steps
E!pected "esult
Page 2 of Pages
<Client> Test Script %continuation sheet&
Project ID
Test ID
Purpose of Test
Test Enironment
Test Steps
E!pected "esult
Page of Pages
CTS #i$i Test Script %front sheet&
Project ID *TS 3roup #ews .iki and Process 1ramework
AUT Title *TS .iki Version $2.4
Iteration 45 Date of Test 46)46)5447
Test ID 45-Team-8rg-*hart-42
Purpose of Test To ensure that:
It is possible to na$igate to the screen showing the Team 8rg *hart
It is possible to $iew the whole Team 8rg *hart( and that it is legible
Test Enironment The test en$ironment is as follows:
*lient 9ardware: I:; T<4 =aptop
Ser$er: *ompany Intranet system
#o other applications should be running on the laptop
The .iki should be running and at the top le$el intro page( with the
login dialog bo, $isible
9and crafted >login data? is held in *:@test-dir@login.dat
Test Steps In the login dialog bo,( the tester should:
=eft click into the >"ser #ame? field and enter >testuser?
=eft click into the >Password? field and enter >password?
=eft click on the >8A? button
8nce the ne,t screen appears( left click on the CTS %rg C&art link in
the left hand na$igation pane
E!pected "esult 8n completing the abo$e steps( the *TS Team 8rg *hart should be
displayed.
'erify that the whole org chart is $isible on the screen.
'erify that the contents of the org chart is legible
Page 2 of 2 Page
'igure ( ) Specimen Completed Test Script for t&e CTS Compan* #i$i project

Das könnte Ihnen auch gefallen