KabInfo.

Net
KabInfo.Net
Test Plan Template
Test Plan Template
Version No 1.00
October 2001
Address
This document contains proprietary information of Planetasia and is tendered subject to the condition that the
information be retained in confidence
Test Plan Guidelines KabInfo.Net
AQS
Document Information Page
Document Cange Details
*A - ADDED M - MODIFIED D - DELETED
CHANGE
NUMBER DATE
NUMBER OF FIGURE,
TABLE OR PARAGRAPH
A* M D
TITLE OR BRIEF DESCRIPTION
CRF Ref. Id.
Document Control Information
Total No. of pages 36
Re!e" Pe#!od 1 Year or arlier
D!st#!$%t!o& T!rou"! Qualit# $or%orate Intranet
!e"ision and Appro"al #ists
No 'e#s!o&
N%($e#
Release Date A%t)o#ed B* Re!e"ed
B*
App#oed
B*
Released B* CRF No.
1. 1.&& &1'1&'(&&1 SP)PT SPG S$ *ead Qualit# N'A
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (
Test Plan Guidelines KabInfo.Net
AQS
DOC$%&NT CONV&NTION'
<Text > Replace text.
Text in Italics with Blue coloured fonts Notes or nstr!ctons to t"e a!t"or. Delete n fnal
for#at.
Delete this page in the final format of your document
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 3
Test Plan Guidelines KabInfo.Net
AQS
Table of Contents
1 INT!OD$CTION.......................................................................................................................... (
$.$ O%ER%IE& OF '('TEM ........................................................................................................... )
$.* '+O,E OF TE'TIN-................................................................................................................. )
$.. ,/R,O'E OF T0I' DO+/MENT................................................................................................. )
$.1 O23E+TI%E' ........................................................................................................................... )
$.1.$ /nt Testn4...................................................................................................................................... 5
$.1.* Inte4raton Testn4............................................................................................................................ 5
$.1.. '6ste# Testn4................................................................................................................................. 5
$.1.1 /ser Acceptance Testn4.................................................................................................................. 5
$.1.7 Enterprse Inte4raton Testn4.......................................................................................................... 5
$.7 TE'T DELI%ERA2LE'................................................................................................................ 5
$.7.$ /nt Testn4 ..................................................................................................................................... 5
$.7.* Inte4raton Testn4 ........................................................................................................................... 5
$.7.. '6ste# Testn4 ................................................................................................................................ 8
$.7.1 /ser Acceptance Testn4 ................................................................................................................. 8
$.7.7 Enterprse Inte4raton Testn4 ......................................................................................................... 8
$.) REFEREN+E' AND 'O/R+E DO+/MENTATION........................................................................... 8
$.5 A22RE%IATION'9 A+RON(M' AND DEFINITION' ......................................................................... 8
2 T&'TIN) 'C*&D$#&............................................................................................................... 10
+ T&A% D&V&#OP%&NT............................................................................................................. 11
..$ TE'TIN- TEAM FORMATION.................................................................................................... $$
..* TRAININ-............................................................................................................................... $$
... ROLE' : RE',ON'I2ILITIE'................................................................................................... $$
, T&'T &NVI!ON%&NT............................................................................................................... 12
1.$ 0ARD&ARE +OM,ONENT' RE;/IRED...................................................................................... $*
1.$.$ 'er<ers ......................................................................................................................................... $*
1.$.* &or=statons.................................................................................................................................. $*
1.* 'OFT&ARE RE;/IREMENT' ................................................................................................. $*
1.*.$ 'er<er Re>!re#ents..................................................................................................................... $*
1.*.* +lent ? &or=staton Re>!re#ents................................................................................................. $*
1.. TOOL' TO 2E /'ED................................................................................................................ $*
1.1 TE'T DATA2A'E'................................................................................................................... $*
- T&'TIN) APP!OAC*............................................................................................................... 1+
( 'TANDA!D' AND P!OC&D$!&'.......................................................................................... 1,
).$ TE'T +A'E............................................................................................................................ $1
).$.$ /nt Test cases............................................................................................................................... $1
).$.* Inte4raton Test cases.................................................................................................................... $1
).$.. '6ste# Test cases......................................................................................................................... $1
).$.1 /ser Acceptance Test cases.......................................................................................................... $1
).$.7 Enterprse Inte4raton Test cases................................................................................................... $1
).* A+TI%ITIE'............................................................................................................................. $1
. T&'T IT&%'.............................................................................................................................. 1-
5.$ IN+L/'ION'- FEAT/RE' TO 2E TE'TED................................................................................... $7
5.* E@+L/'ION'- FEAT/RE' NOT TO 2E TE'TED.......................................................................... $7
5.. ',E+IFI+ E@+L/'ION' ......................................................................................................... $7
5.1 ,RIORITIAATION..................................................................................................................... $7
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT +
Test Plan Guidelines KabInfo.Net
AQS
/ T&'T &NT!ANC& 0 &1IT C!IT&!IA......................................................................................... 1(
8.$ ENTRAN+E +RITERIA............................................................................................................ $)
8.$.$ /nt Testn4 ................................................................................................................................... $)
8.$.* Inte4raton Testn4.......................................................................................................................... $)
8.$.. '6ste# Testn4............................................................................................................................... $)
8.$.1 /ser Acceptance Testn4................................................................................................................ $5
8.$.7 Enterprse Inte4raton Testn4........................................................................................................ $5
8.* E@IT +RITERIA....................................................................................................................... $5
8.*.$ /nt Testn4 ................................................................................................................................... $5
8.*.* Inte4raton Testn4 ......................................................................................................................... $5
8.*.. '6ste# Testn4 .............................................................................................................................. $8
8.*.1 /ser Acceptance Testn4................................................................................................................ $8
8.*.7 Enterprse Inte4raton Testn4........................................................................................................ $8
2 3$A#I4ICATION P!OVI'ION'................................................................................................ 12
B.$ +RITERIA FOR TE'T +OM,LETION.......................................................................................... $B
B.* A,,LI+ATION RELEA'E +RITERIA............................................................................................ $B
10 T&'T '$'P&N'ION0!&'$%PTION !&3$I!&%&NT'.........................................................20
$C.$ '/',EN'ION +RITERIA........................................................................................................ *C
$C.* RE'/M,TION +RITERIA........................................................................................................ *C
11 T&'T ANA#5'I'...................................................................................................................... 21
$$.$ ANAL(AIN- AND RE,ORTIN-................................................................................................. *$
$$.* ,RO2LEM DETERMINATION AND +ORRE+TION.......................................................................*$
$$.. DEFE+T MEA'/REMENT ...................................................................................................... *$
12 D&4&CT %ANA)&%&NT ...................................................................................................... 22
1+ T&'T %&T!IC.......................................................................................................................... 2+
......................................................................................................................................... *.
1, 'TAT$' !&PO!TIN)............................................................................................................. 2,
1- APP&NDI16 T5P&' O4 T&'TIN)........................................................................................... 2-
$7.$ DATA AND DATA2A'E INTE-RIT( TE'TIN-............................................................................. *7
$7.* 2/'INE'' +(+LE TE'TIN-................................................................................................... *)
$7.. /'ER INTERFA+E TE'TIN-................................................................................................... *5
$7.1 ,ERFORMAN+E ,ROFILIN- .................................................................................................. *8
$7.7 LOAD TE'TIN-..................................................................................................................... *B
$7.) 'TRE'' TE'TIN-................................................................................................................. .C
$7.5 %OL/ME TE'TIN-................................................................................................................ .$
$7.8 'E+/RIT( AND A++E'' +ONTROL TE'TIN-.......................................................................... .*
$7.B FAIL/RE ? RE+O%ER( TE'TIN-............................................................................................. ..
$7.$C +ONFI-/RATION TE'TIN-.................................................................................................. .7
$7.$$ IN'TALLATION TE'TIN-....................................................................................................... .)
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT ,
Test Plan Guidelines
AQS
1 Introduction
1.1 O"er"ie7 of '8stem
<A bref Descrpton abo!t t"e s6ste#>
<Enter 6o!r text "ere>
1.2 'cope of Testing
<Ite#s n<ol<eD n /nt9 ?Inte4raton? '6ste#?/ser Acceptance Testn4 ?Enterprse Inte4raton Testn4
as a4reeD !pon anD clearl6 specfc an6 Non co<era4e of testn4 scope. Lst an6 ass!#pton anD
constrants #aDe D!rn4 t"e De<elop#ent of t"s Doc!#ent t"at #a6 #pact t"e Des4n9 De<elop#ent
or #ple#entaton of testn4. >
<Enter 6o!r text "ere>
1.+ Purpose Of Tis Document
<T"s Doc!#ent "as to be taloreD accorDn4 to t"e t6pe of testn4 na#el6 E/nt9 ?Inte4raton? '6ste#?
/ser Acceptance Testn4 ?Enterprse Inte4raton Testn4>
,reparaton for t"s test conssts of t"ree #aFor sta4esG
Test Planning Detals t"e act<tes9 DepenDences9 effort9 test #etrcs collecton #et"oDolo4es
anD testn4 stoppa4e crtera.
T"e Test Approac sets t"e scope of E/T?IT?'T?/AT?EITH Testn49 t"e o<erall strate46 to be
aDopteD9 t"e act<tes to be co#pleteD9 t"e 4eneral reso!rces re>!reD anD t"e effect<e #et"oDs
anD processes to be !seD to test t"e release. It also Detals t"e act<tes9 DepenDences anD effort
re>!reD to conD!ct t"e Test.
Test Conditions0Cases Detals to be folloIeD n preparaton of Test +ases. JE.4.9 Des4nn4 t"e
tests to be appleD9 t"e Data to be processeD9 t"e a!to#ateD testn4 co<era4e anD t"e expecteD
res!lts.K
*o7 to $se tis document6
T"s Doc!#ent ser<es as a -!Delne Doc!#ent for t"e entre test plans.
$. A co#bneD test plan for !nt9 nte4raton anD s6ste# testn4 can be prepareD !sn4 t"s 4!Delne b6
selectn4 t"e necessar6 sectons fro# t"e 4!Delne. Tec" LeaD?Test LeaD a!t"ors t"s plan. Eac" t6pe of test
plan "as to be !pDateD D!rn4 t"e respect<e p"ases of t"e A;' fra#eIor=.
*. For !ser acceptance testn4 t"s 4!Delne can also be !seD9 f t"ere s no specfc test plan a<alable It" t"e
clent. T"s plan s a!t"oreD et"er b6 t"e +lent Rep or t"e ,roFect Mana4er n absence of t"e +lent.
.. For enterprse nte4raton testn4 a separate plan "as to be a!t"oreD !sn4 t"s 4!Delne n accorDance It"
t"e clent. 'nce t"s t6pe of testn4 s a specfc n nat!re. T"e ,roFect Mana4er n cons!ltaton It" t"e
clent anD t"rD part6 <enDors a!t"ors t"s plan.
AppenDxG T6pes of testn4 are DetaleD n t"s secton. 'nce t"ere s no separate test proceD!re t6pes of testn4
are DetaleD "ere. T"s can be appenDeD I"ere<er t"e !sa4e specfes.
1., Ob9ecti"es
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 6
Test Plan Guidelines
AQS
1.,.1 $nit Testing
T"e co#plete co<era4e of LLD or DD s"o!lD be #appeD a4anst t"e coDe De<elopeD.
T"e /nt coDe s of 04" ;!alt6.
+oDe Ial= t"ro!4" s s!ccessf!ll6 co#pleteD.
To Ens!re t"at t"e /nt pro4ra#s Ior=s It" less or ne4l4ble rs=s.
,ro<Des constr!ct<e np!ts for testn4 process #pro<e#ent t"ro!4" test #etrcs.
1.,.2 Integration Testing
T"e co#plete 0LD or DD s"o!lD be #appeD a4anst t"e coDe De<elopeD.
To Ens!re t"at t"e nte4rateD co#ponents Ior=s It" less or ne4l4ble rs=s.
,ro<Des constr!ct<e np!ts for testn4 process #pro<e#ent t"ro!4" test #etrcs.
1.,.+ '8stem Testing
T"e f!nctonalt6 n-b!lt nto t"e softIare as specfeD n t"e b!sness re>!re#ent
specfcaton ? f!nctonal specfcaton J2R'?F'K.
T"e softIare s of "4" >!alt6.
Ens!re t"at s6ste# Ior=s It" less or ne4l4ble rs=s
,ro<Des constr!ct<e np!ts for testn4 process #pro<e#ent t"ro!4" test #etrcs.
1.,., $ser Acceptance Testing
T"e f!nctonalt6 n-b!lt nto t"e softIare as specfeD n t"e +ontract?'er<ce Le<el
A4ree#ent.
1.,.- &nterprise Integration Testing
T"e co#plete co<era4e of 2R'9 F'9 0LD9 anD LLD s"o!lD be #appeD a4anst t"e coDe
De<elopeD.
To Ens!re t"at t"e nte4rateD co#ponents Ior=s It" less or ne4l4ble rs=s.
T"e De<elopeD applcaton #oD!le s"o!lD collaborate It" t"e #an applcaton at t"e
clentLs ste
,ro<Des constr!ct<e np!ts for testn4 process #pro<e#ent t"ro!4" test #etrcs.
1.- Test Deli"erables
All t"e Del<erables s"o!lD be n +M Tool
1.-.1 $nit Testing
TesteD /nt coDe
/nt Test cases
/nt Test Reports
+oDe Ial= t"ro!4" Re<eI Report
1.-.2 Integration Testing
TesteD Inte4rateD +oDe
Inte4raton test cases
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT -
Test Plan Guidelines
AQS
Inte4raton Test Reports
,re Test <erfcaton For#
1.-.+ '8stem Testing
'6ste# TesteD Exec!tables
'6ste# Test cases Jf a4reeD It" +lent as per contractK
Defect Lo4 Report
Lst of Open Defects
,ost Test %alDaton For#
1.-., $ser Acceptance Testing
/ser Acceptance Test +ases
/ser Acceptance Test Report
,roble# Report
1.-.- &nterprise Integration Testing
Enterprse Inte4raton TesteD Exec!tables.
Enterprse Inte4raton test cases Jf a4reeD It" t"e clent as per contractK
Enterprse Inte4raton Test Reports
An6 Open Iss!es Lst
Release +learance Note
1.( !eferences And 'ource Documentation
+ontract?'er<ce Le<el A4ree#ent JReference DetalsK
2!sness Re>!re#ent 'pecfcaton %er. <M.MM> anD DateG <DD?MM?((((>
F!nctonal 'pecfcaton %er. <M.MM> anD DateG <DD?MM?((((>
04" Le<el Doc!#ent. <M.MM> anD DateG <DD?MM?((((>
LoI Le<el Doc!#ent. <M.MM> anD DateG <DD?MM?((((>
Des4n Doc!#ent. <M.MM> anD DateG <DD?MM?((((>
,ro4ra# ,lan <M.MM> anD DateG <DD?MM?((((>
Acceptance +rtera9 rece<eD fro# t"e clent JReference DetalsK9 f an6
+lent '!ppleD Materals9 f an6
1.. Abbre"iations: Acron8ms and Definitions
A$$#e!at!o&s .
A2#o&*(s
Def!&!t!o&s
.nit Testin" .nit testin" /o0ers t!e inte"ral %art of t!e unit of a soft1are 1or2 %rodu/t. Pri3aril# t!e indi0idual
%ro"ra3s 1ould be /onsidered in e4e/utin" t!is 3et!od of testin".
Inte"ration Testin" Inte"ration testin" is a s#ste3ati/ testin" te/!ni5ue for un/o0erin" de0iations related to interfa/in"
bet1een 0arious soft1are units.
S#ste3 Testin" S#ste3 testin" at Planetasia is /onsidered onl# to t!e e4tent of fun/tionalit# of t!e A%%li/ation6 it
does not in/lude t!e /o3bined testin" of !ard1are and soft1are /o3%onents.
.ser A//e%tan/e Testin" T!e test /ondu/ted b# t!e .ser or t!e $lient 7e%. on t!e entire A%%li/ation. In !ouse tea3 /an
/ondu/t t!is also.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 8
Test Plan Guidelines
AQS
A$$#e!at!o&s .
A2#o&*(s
Def!&!t!o&s
nter%rise Inte"ration
Testin" 9IT:
T!e test /ondu/ted after inte"ratin" t!e s#ste3 de0elo%ed b# Planetasia6 1it! alread# e4istin"
s#ste3s ;ba/2)end or ot!er a%%li/ation 3odules< at t!e /lient site.
7e"ression Testin" 7e testin" of t!e Defe/ts fi4es /onstitute 7e"ression testin".
=7S =usiness 7e5uire3ent S%e/ifi/ation
>S >un/tional S%e/ifi/ation
*?D *i"! ?e0el Desi"n 9T!is do/u3ent is used for ?ar"er Pro@e/ts )If t!e Pro@e/t is of a tenure of 3ore
t!an 3 Mont!s it is /onsider a lar"er %ro@e/t6 but a"ain it is situational based.:
??D ?o1 ?e0el Desi"n 9T!is do/u3ent is used for ?ar"er Pro@e/ts )If t!e Pro@e/t is of a tenure of 3ore
t!an 3 Mont!s it is /onsider a lar"er %ro@e/t6 but a"ain it is situational based.:
DD Desi"n Do/u3ents 9A!ere t!ere is no need for t!e de0elo%3ent of *?D and ??D6 t!is do/u3ent is
used 1!i/! is a /o3bination of *?D and ??D:
.T$ .nit Test /ases
IT$ Inte"ration Test $ase
ST$ S#ste3 Test /ases
AT$ .ser A//e%tan/e Test /ases
.TP .nit Test Plan
ITP Inte"ration Test Plan
STP S#ste3 Test Plan
.AT .ser A//e%tan/e Test Plan
DTS Defe/t Tra/2in" S#ste3 ) In !ouse tool fa/ilitates to aut!or t!e test /ases6 tra/2 defe/ts and
"enerates Test Measure3ents.
PDA Pro@e/t Definition Aor2s!o%
De0elo%er Pro"ra33er or a 3e3ber of t!e De0elo%3ent tea3
T? Test ?ead
T Test n"ineer
Te/!. ?ead Te/!ni/al ?eader or Pro@e/t ?ead
PM Pro@e/t Mana"er
$lient 7e%. $lient 7e%resentati0e
QA 7e%. Me3ber of t!e Qualit# assuran/e Grou%.
$$ Tool $onfi"uration $ontrol Tool
7MS 7esour/e Mana"e3ent S#ste3
A%%li/ation 7efers to t!e de0elo%ed soft1are %rodu/t.
.BG .ser 4%erien/e Grou%
4%lorator# Testin" T!e test e4e/ution6 1!i/! is /arried out 1it! out test /ases or 1it!out an# %lannin". ;S%e/ifi/all# t!is
t#%e of testin" is /ondu/ted in /ontent)ri/! a%%li/ation<
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT C
Test Plan Guidelines
AQS
2 Testing Schedule
<T"s secton s"all specf6 t"e sc"eD!ln4 of t"e testn4 act<tes9 n t"e for# of Testn4 -antt +"art or
an6 ot"er s!table #et"oD9 I"c" enables to plan anD exec!te t"e testn4 relateD act<tes9 n t"e
entre De<elop#ent c6cle.
Reso!rces for testn4 t"e softIare are ass4neD earl6 eno!4" to pro<De for aDe>!ate test
preparaton.
It co!lD also "a<e t"e reference to t"e Testn4 'c"eD!le9 I"en t s Done It" so#e ot"er tool l=e M'-
,roFect anD t s"o!lD be constantl6 !pDateD>

</nt ?Inte4raton ?'6ste#?/ser Acceptance ? Enterprse Inte4raton Test sc"eD!leG In case Testn4 s
a part of ,roFect Lfe c6cle act<t69 t"e Testn4 sc"eD!le s"o!lD be a part of ,roFect -antt. +"art9 else
create a separate Testn4 -antt. +"art anD Ln= to t"s secton>
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1&
Test Plan Guidelines
AQS
3 Team Development
+.1 Testing Team 4ormation
<T"s secton s"all specf6 t"e neeD for t"e testn4 tea#9 n!#ber of #e#bers re>!reD9
'=lls re>!reD for t"e #e#ber9 etc. In case of EIT Onste anD Offs"ore tea# can be for#eD>
<Enter 6o!r text "ere>
+.2 Training
<Menton t"e trann4 re>!re#ents of t"e test tea# #e#bers9 f re>.
In case of EIT 'pecfc ,roFect relateD Trann4 ?KnoIleD4e Transfer can be pro<DeD to t"e Tea#s>
<Enter 6o!r text "ere>
+.+ !oles ; !esponsibilities
<Menton t"e pr#e responsbltes of t"e tea# #e#bers9 tea# leaDs9 f explctl6 DefneD>
<Enter 6o!r text "ere>
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 11
Test Plan Guidelines
AQS
4 Test Environment
,.1 *ard7are components re<uired
<T"s secton s"all specf6 t"e "arDIare re>!re#ents for conD!ctn4 eac" t6pe of test act<tes>
,.1.1 'er"ers
<Menton "arDIare co#ponents t"at #a6 be re>!reD for t"e ser<ers>
<Enter 6o!r text "ere>
,.1.2 =or>stations
<Menton t"e "arDIare co#ponents re>!reD for t"e Ior=statons>
<Enter 6o!r text "ere>
,.2 'oft7are !e<uirements
,.2.1 'er"er !e<uirements
<Menton t"e softIare re>!re#ents of t"e 'er<erJsK>
<Enter 6o!r text "ere>
,.2.2 Client 0 =or>station !e<uirements
<Menton t"e softIare re>!re#ents of t"e +lentJsK>
<Enter 6o!r text "ere>
,.+ Tools to be used
<Menton t"e tools to be !seD or an6 tools pro<DeD b6 t"e clent>
<Enter 6o!r text "ere>
,., Test Databases
<Menton t"e separate Databases createD or pro<DeD>
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1(
Test Plan Guidelines
AQS
5 Testing Approach
<T"s secton s"all specf6 t"e <aro!s testn4 approac" toIarDs Dfferent t6pes of testn4 In case of
EIT t"e clent specfc re>!re#ents "as to be DetaleD n t"s secton. >
<T"e Test 'trate46 presents t"e reco##enDeD approac" to t"e testn4 t"e tar4et-of-test.
For eac" t6pe of test9 pro<De a Descrpton of t"e test anD I"6 t s ben4 #ple#enteD anD exec!teD.
If a t6pe of test Ill not be #ple#enteD anD exec!teD9 nDcate n a sentence statn4 t"e test Ill not
be #ple#enteD ? exec!teD anD statn4 t"e F!stfcaton9 s!c" as NT"s test Ill not be #ple#enteD ?
exec!teD. T"s test s not approprate OP>
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 13
Test Plan Guidelines
AQS
6 Standards and Procedures
(.1 Test Case
<'tate t"e stanDarDs establs"eD for Irtn4 t"e !nt9 Inte4raton9 '6ste#9 /ser Acceptance9
Enterprse Inte4raton test cases. >
(.1.1 $nit Test cases
ReferG Test +ase Te#plate
(.1.2 Integration Test cases
ReferG Test +ase Te#plate
(.1.+ '8stem Test cases
ReferG Test +ase Te#plate
(.1., $ser Acceptance Test cases
EIn case t"ere s no specfc np!t toIarDs t"e test cases fro# t"e clent9 Ie can !se t"e
stanDarD test case te#plate -A;'H
ReferG Test +ase Te#plate
(.1.- &nterprise Integration Test cases
EIn case t"ere s no specfc np!t toIarDs t"e test cases fro# t"e clent9 Ie can !se t"e
stanDarD test case te#plate -A;'H
ReferG Test +ase Te#plate
(.2 Acti"ities
E2ref abo!t t"e stanDarDs?proceD!res c"osen for test plannn49 conD!ctn4 t"e test reportn49
t"e test res!lts anD Anal6ss?E<al!aton of t"e test res!ltsH
EFo# e. g., S*ste( Test!&g+
Test Plan te3%lates !a0e ta2en out fro3 AQS. Test Plan is %re%ared based on Pro"ra3 Plan. An# 3odifi/ation in Pro"ra3 %lan 1ill !a0e i3%a/t on
test %lan.
Detailed stud# !as to be done on =7S'>S do/u3ents %ro0ided b# de0elo%3ent tea3.
Test $ases !a0e to be de0elo%ed based on t!e abo0e do/u3ents.
T!e de0elo%ed Test $ases !as to be re0ie1ed b# Test Tea3 Me3bers and Tea3 ?ead.
Settin" u% of Test n0iron3ent ;*ard1are'Soft1are'Ser0ers<6 Defe/ts 7e%ortin" Tool'Me/!anis3.
$olle/t t!e .nit Test 7esults fro3 de0elo%3ent tea36 /ode 1al2 t!rou"! results and %re)test 0erifi/ation for3 !as to be filled b# de0elo%3ent tea3
lead.
Module'Pro@e/t !as to be ta2en out fro3 $M Tool 1it! a%%ro%riate 0ersions.
A%%li/ation of test /ases to t!e 3odules and t!e test results !as to be do/u3ented in MS)4/el S!eet'Defe/ts 7e%ortin" Tool and t!e sa3e s!ould
be notified to de0elo%3ent tea3.
7e"ression testin" !as to be done on t!e ne4t release of t!e Module'Pro@e/t.
An# differen/e of o%inions raised6 due to Defe/ts raised b# t!e test en"ineers6 !as to be resol0ed t!rou"! Issue Meetin"s.
>inall# Test su33ar# !as to be %resented.:
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1+
Test Plan Guidelines
AQS
Test Items

..1 Inclusions? 4eatures to be tested
[Mention the features which are part of the development and which are to be included from testing by briefing
with justification for such an action.]
<Enter 6o!r text "ere>
..2 &@clusions? 4eatures not to be tested
[Mention the features which are part of the development and which are to be excluded from testing by briefing
with justification for such an action.]
<Enter 6o!r text "ere>
..+ 'pecific &@clusions
[Mention the features from earlier freeze release, which are to be excluded from testing by briefing
with justification for such an action. Such exclusion may be because of reusable components from
library, third party interface, feature from other dependent module]
<Enter 6o!r text "ere>
NoteG Excl!sons anD specfc excl!sons s"all be arr<eD at n cons!ltaton It" De<elop#ent9 ,roFect
Mana4e#ent9 anD t"e clent. TraDe-off Decsons n<ol<n4 scope?effort?sc"eD!le?>!alt69 I"c" #a6 res!lt n
b!sness aD<anta4es9 s"all be !seD as a crteron n t"s. T"s pla6s #aFor role n reD!cn4 test sc"eD!le anD
effort.
.., PrioritiAation
[riefly state the testing priorities based on the re!uirements priorities identified
in the business re!uirements specification or the functional specification]
<Enter 6o!r text "ere>
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1,
Test Plan Guidelines
AQS
! Test Entrance " E#it $riteria
/.1 &ntrance Criteria
T"e Entrance +rtera specfeD b6 t"e ,roFect Mana4er?Tec". LeaD?Test LeaD? +lent Rep. s"o!lD be
f!lflleD before Test can co##ence. In t"e e<ent9 t"at an6 crteron "as not been ac"e<eD9 t"e Test
#a6 co##ence9 f ,roFect Mana4er?Tec". LeaD?Test LeaD? +lent Rep. s n f!ll a4ree#ent t"at t"e rs=
s #ana4eable anD t"e sa#e "as to be Doc!#enteD n Test ,lan.

/.1.1 $nit Testing
Re<eIeD anD '4neD off /nt Test plan s"o!lD exst n ++ Tool.
All "!#an reso!rces as per plan #!st be ass4neD anD n place.
T"e En<ron#ents anD reso!rces #!st be n place9 anD #!st be a<alable for testn4
Re<eIeD ,ro4ra# 'pecfcatons s"all be n place.
Re<eIeD /nt Test +ases s"o!lD exst n t"e ++ Tool.
T"e applcaton s"o!lD be nte4rateD It" t"e /ser Interface te#plates fro# /@-
T"e baselne-De<elopeD coDe s"o!lD exst n t"e ++ Tool.
["lease add additional entrance criteria #if any$ here]
/.1.2 Integration Testing
Re<eIeD anD '4neD off Inte4raton Test ,lan
Re<eIeD Inte4raton Test cases.
All "!#an reso!rces as per plan #!st be ass4neD anD n place.
T"e TesteD /nt coDes s"o!lD exst n t"e ++ Tool.
T"e Test Res!lts s"o!lD exst n t"e ++ Tool.
T"e -/I Res!lts s"o!lD exst n t"e ++ Tool.
T"e +oDe Ial= t"ro!4" Res!lts s"o!lD exst n t"e ++ Tool.
T"e En<ron#ents anD reso!rces #!st be n place9 anD #!st be a<alable for testn4
["lease add additional entrance criteria #if any$ here]
/.1.+ '8stem Testing
T"e /nt anD Inte4rateD Test cases s"o!lD exst n t"e ++ Tool
T"e /nt anD Inte4rateD Test coDe s"o!lD exst n t"e ++ Tool.
T"e /nt anD Inte4rateD Test Res!lts s"o!lD exst n t"e ++ Tool.
T"e -/I Test Res!lts s"o!lD exst n t"e ++ Tool
T"e +oDe Ial= t"ro!4" Res!lts are placeD n t"e ++ Tool.
Re<eIeD anD appro<eD '6ste# Test ,lan s"o!lD exst n t"e ++ Tool.
Re<eIeD anD appro<eD '6ste# Test cases s"o!lD exst n t"e ++ Tool.
,re Test %erfcaton For# Exst.
T"e En<ron#ents anD reso!rces #!st be n place9 anD #!st be a<alable for testn4
All "!#an reso!rces as per plan #!st be ass4neD anD n place.
["lease add additional entrance criteria #if any$ here]
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 16
Test Plan Guidelines
AQS
/.1., $ser Acceptance Testing
All t"e Re<eIeD /ser Acceptance Test ,lan anD Test cases s"o!lD exst n t"e ++ Tool.
T"e '6ste# Test Res!lts ?Defect Lo4 s"o!lD exst n t"e ++ Tool.
Lst of Open Iss!es ?Open Defects.
All "!#an reso!rces as per plan #!st be ass4neD anD n place.
T"e En<ron#ents anD reso!rces #!st be n place9 anD #!st be a<alable for testn4
as
'!44esteD anD a4reeD !pon b6 t"e +lent Rep.
["lease add additional %xit criteria #if any$ here]
/.1.- &nterprise Integration Testing
All te belo7 mentioned items sould be a"ailable at te &IT 'ite.
Re<eIeD anD '4neD off Enterprse Inte4raton Test ,lan
Re<eIeD Enterprse Inte4raton Test cases.
All "!#an reso!rces as per plan #!st be ass4neD anD n place.
T"e '6ste# TesteD exec!tables.
T"e +oDe Ial= t"ro!4" Res!lts
T"e +onsolDateD Test Res!lts
An6 Open Iss!es after '6ste# Testn4
An6 clent pro<DeD specfc testn4 nstr!ctons
Applcaton Deplo6#ent 0arDIare anD 'oftIare
Test Data to test t"e nterface It" t"e #an applcaton
Test Dr<ers?'oc=ets? A,Is anD?or an6 ot"er relateD co#ponents for testn4.
T"e En<ron#ents anD reso!rces #!st be n place9 anD #!st be a<alable for testn4
["lease add additional entrance criteria #if any$ here]
/.2 &@it Criteria
/.2.1 $nit Testing
All t"e Re<eIeD Test cases s"o!lD be exec!teD.
T"e Test +ases are placeD n t"e ++ Tool.
All t"e Defects raseD D!rn4 t"e /nt Testn4 s"o!lD be fxeD9 Re testeD anD closeD.
T"e TesteD /nt +oDes are placeD n t"e ++ Tool.
T"e /nt Test Res!lt s placeD n t"e ++ Tool.
T"e -/I Test Res!lts are placeD n t"e ++ Tool.
T"e +oDe Ial= t"ro!4" Res!lts are placeD n t"e ++ Tool.
["lease add additional exit criteria #if any$ here]
/.2.2 Integration Testing
All t"e Re<eIeD Inte4raton Test cases s"o!lD be exec!teD.
T"e Inte4raton Test cases are placeD n t"e ++ Tool.
All t"e Defects raseD D!rn4 t"e Inte4raton Testn4 s"o!lD be fxeD9 Re testeD anD
closeD.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1-
Test Plan Guidelines
AQS
All t"e ,ro4ra#s9 I"c" "a<e !nDer4one Inte4raton testn49 are placeD n t"e ++ Tool.
T"e Inte4raton Test Res!lt s placeD n t"e ++ Tool.
T"e +oDe I"c" "as !nDer4one t"e nte4raton testn4 s"o!lD exst n t"e ++ Tool.
["lease add additional exit criteria #if any$ here]
/.2.+ '8stem Testing
All t"e Re<eIeD s6ste# test cases s"o!lD be exec!teD.
T"e '6ste# Test Res!lts ?Defect Lo4 s"o!lD exst n t"e ++ Tool.
,reparaton of ,ost Test %alDaton For#.
No Defects It" 04" prort6 anD 'e<ert6 Exsts.
Lst of Open Iss!es ?Open Defects.
If an6 #eD!# or loI-prort6 Defects .e. se<ert6 $ anD * are o!tstanDn4 - t"e
#ple#entaton rs= #!st be s4neD off.
T"e Exec!tables fro# s6ste# testn4 s"o!lD exst n ++ Tool.
["lease add additional %xit criteria #if any$ here]
/.2., $ser Acceptance Testing
/ser Acceptance +ertfcate ss!eD b6 t"e +lent as acceptance of t"e Applcaton or
Internal Acceptance +ertfcate.
,roble# Report For# EIf an6 Iss!esH
["lease add additional %xit criteria #if any$ here]
/.2.- &nterprise Integration Testing
Re<eIeD Enterprse Inte4raton Test cases s"o!lD be exec!teD.
,roble# Report For# Ef an6 ss!esH
Lst of Open Iss!es ?Open Defects.
Release Note
["lease add additional %xit criteria #if any$ here]
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 18
Test Plan Guidelines
AQS
% &uali'ication Provisions
2.1 Criteria for test completion
[State the criteria to be adopted for the test completion& it can be based on the functionalities chosen, or a
suitable norm as agreed upon with the customer based on the test metric.
'his section only indicates completion of the test execution& however overall testing process completion
(s explained in the %xit criteria.]
2.2 Application !elease Criteria
E'tate t"e crtera aDopteD for t"e test co#pleton anD applcaton releases l=e test #etrcs9
conf4!raton #ana4e#ent9 stablt69 perfor#ance benc"#ar=9 etc.H
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 1C
Test Plan Guidelines
AQS
1( Test Suspension")esumption
)e*uirements
[State the conditions under which the test execution can be suspended and also under what
circumstances it can be resumed based on the established procedure.]
[In case of EIT this has to be clearly discussed with the client and any special clauses can be
appended in this section]
10.1 'uspension Criteria
An6 ,roble# n t"e "arDIare ? 'oftIare Reso!rces
Fal!re of proper f!nctonn4 of 'er<ers? NetIor=s
An6 a#b4!tes n f!nctonalt6Ls
An6 slppa4e of pro4ra#s sc"eD!les9 I"c" #a6 "nDer planneD testn4 act<tes.
10.2 !esumption Criteria
Abo<e Iss!es resol<eD9 Iss!e #eetn4s It" peer tea# or co#ponent tea# or an6 ot"er
Met"oDolo46 as DefneD at t"e t#e ,roFect Talorn4.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (&
Test Plan Guidelines
AQS
11 Test Anal+sis
11.1 Anal8Aing And !eporting
[Mention the test results analysis and reporting responsibilities if explicitly defined]
<Enter 6o!r text "ere>
11.2 Problem Determination And Correction
[Mention the problem determination and correcting responsibilities for the identified )efects
in testing]
<Enter 6o!r text "ere>
11.+ Defect %easurement
["rovide details on the way in which )efects are reported and handled]
<Enter 6o!r text "ere>

'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (1
Test Plan Guidelines
AQS
12 De'ect ,anagement
D!rn4 Testn49 Defects Ill be recorDeD !sn4 [enter the name of the tool #if any$ or method that will be
used]. T"e Defects Ill be re<eIeD anD prortQeD anD ass4neD for fx9 f re>!reD. Defects9 I"c" are
a4reeD as <alD9 Ill be cate4orQeD as folloIsG -
[Depending on the nature of the proect the defect se!erity may change for e.g." for a content rich proect# the color !ariation
may be a maor se!erity]
Defe2t See#!t* Des2#!pt!o&
>atal Defe/ts t!at 1ould result in /o3%lete o3ission of a re5uire3ent6 fro3 t!e s/o%e of t!e do/u3ent ' /ode or
a%%li/able standards and "uidelines.
Ma@or Defe/ts 1it! obser0able de%artures fro3 t!e standard or "uidelines resultin" in in/o3%lete and a3bi"uous
do/u3entation and %ro"ra3 /ode
Minor $os3eti/ %roble3s li2e s%ellin"6 for3attin" et/.
$os3eti/'
Su""estion
Su""estionsD T!ese are %ri3aril# su""estions for i3%ro0in" ' en!an/in" t!e fun/tionalit#.
Defe2t Stat%s Des2#!pt!o&
E%en Defe/ts 1!en re%orted and not re0ie1ed b# de0elo%3ent tea3
>i4ed T!e fi4ed status indi/ates t!at a /!an"e 1as 3ade to t!e /ode and 1ill be a0ailable in t!e ne4t build
Ne4t P!ase Defe/ts t!at /an not be fi4ed in t!is release
Need 3ore
infor3ation
Need 3ore infor3ation or NMI indi/ates t!at t!e de0elo%er does not !a0e enou"! infor3ation to du%li/ate or fi4
t!e Defe/ts
$an Ft be >i4ed T!ere 3a# be e4tenuatin" /ir/u3stan/es 1!ere Defe/ts 1ill not be fi4ed be/ause of te/!nolo"#6 ti3e
/onstraints6 and a ris2 of de stabiliGin" t!e /ode or ot!er users. A better status to use is not be fi4ed
$losed Enl# t!e defe/t re%orter uses t!is status6 de0elo%ers or 3ana"ers /annot use t!is status. If a Defe/ts isnFt
re%rodu/ible b# t!e assi"ned de0elo%er or Defe/ts 0erifier t!e Defe/ts re%orter needs a /!an/e to /larif# or add
to t!e Defe/ts.
7e0ie1ed T!is status is onl# "i0en b# t!e Pro@e/t Mana"ers. T!e# "i0e t!is on/e t!e# re0ie1 a defe/t and assi"n t!e3 to
t!e de0elo%er for fi4in" it.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT ((
Test Plan Guidelines
AQS
13 Test ,etric
EIDentf6 s!table test #etrc baseD on t"e co#plext6 of t"e applcaton anD also as an np!t for #pro<e#ent of t"e testn4
processH
NoteG +!sto#er #a6 also "a<e a role n selectn4 a s!table test #etrc.
Defect Denst6 R Total no. of Defects ?'Qe of t"e ,roD!ct
&e4"teD Defect Denst6 R Total no. of &e4"teD Defects ? 'Qe of t"e proD!ct
Defect Denst6 ,rofle R No. of an6 partc!lar t6pe of Defect ? Total no. of Test Defects
Internal Test effcenc6 R No. of Testn4 Defects fo!nD nternall6 ? Total No. of test Defects JInternal
S Acceptance TestK
,roFect Ise A<4. Defect A4e R E,"ase JDetecteD - IntroD!ceDK * No. of DefectsH ?Total No. of
Defects.

'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (3
Test Plan Guidelines
AQS
14 Status )eporting
[In case EIT any specific reporting can also be appended in this section.]
Test preparaton anD pro4ress Ill be for#all6 reporteD D!rn4 a $ee%ly Status &eeting. T"e
attenDees at t"s #eetn4 areG
-ro!p 0eaD
,roFect Mana4er
Tec" LeaD
De<elop#ent Tea#
;!alt6 Representat<e ?;!alt6 0eaD
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (+
Test Plan Guidelines
AQS
15 Appendi#- T+pes o' Testing
1-.1 Data and Database Integrit8 Testing
['he databases and the database processes should be tested as a sub*system within the . 'hese sub*systems
should be tested without the target*of*test+s ,ser (nterface #as the interface to the data$. -dditional research
into the )MS needs to be performed to identify the tools . techni!ues that may exist to support the testing
identified below.]
Test Objective: Ensure Database access methods and processes function properly and
without data corruption.
Technique: Invoke each database access method and process seedin! each with valid
and invalid data "or requests for data#.
Inspect the database to ensure the data has been populated as intended all
database events occurred properly or review the returned data to ensure
that the correct data was retrieved "for the correct reasons#
$ompletion
$riteria:
%ll database access methods and processes function as desi!ned and
without any data corruption.
&pecial
$onsiderations:
Testin! may require a D'(& development environment or drivers to enter
or modify data directly in the databases.
)rocesses should be invoked manually.
&mall or minimally si*ed databases "limited number of records# should be
used to increase the visibility of any non+acceptable events.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (,
Test Plan Guidelines
AQS
1-.2 Business C8cle Testing
[usiness /ycle 'esting should emulate the activities performed on the over time. - period should be
identified, such as one year, and transactions and activities that would occur during a year+s period should be
executed. 'his includes all daily, wee0ly, monthly cycles and events that are date sensitive, such as tic0lers.]
Test Objective Ensure proper tar!et+of+test and back!round processes function accordin!
to required business models and schedules.
Technique: Testin! will simulate several business cycles by performin! the followin!:
The tests used for tar!et+of+test,s function testin! will be modified -
enhanced to increase the number of times each function is e.ecuted to
simulate several different users over a specified period.
%ll time or date sensitive functions will be e.ecuted usin! valid and invalid
dates or time periods.
%ll functions that occur on a periodic schedule will be e.ecuted - launched
at the appropriate time.
Testin! will include usin! valid and invalid data to verify the followin!:
The e.pected results occur when valid data is used.
The appropriate error - warnin! messa!es are displayed when invalid data
is used.
Each business rule is properly applied.
$ompletion
$riteria:
%ll planned tests have been e.ecuted.
%ll identified defects have been addressed.
&pecial
$onsiderations:
&ystem dates and events may require special support activities
'usiness model is required to identify appropriate test requirements and
procedures.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (6
Test Plan Guidelines
AQS
1-.+ $ser Interface Testing
[,ser (nterface testing verifies a user+s interaction with the software. 'he goal of ,( 'esting is to ensure that
the ,ser (nterface provides the user with the appropriate access and navigation through the functions of the
target*of*test. (n addition, ,( 'esting ensures that the objects within the ,( function as expected and conform
to corporate or industry standards.]
Test Objective: /erify the followin!:
0avi!ation throu!h the tar!et+of+test properly reflects business functions
and requirements includin! window to window field to field and use of
access methods "tab keys mouse movements accelerator keys#
1indow objects and characteristics such as menus si*e position state
and focus conform to standards.
Technique: $reate - modify tests for each window to verify proper navi!ation and
object states for each application window and objects.
$ompletion
$riteria:
Each window successfully verified to remain consistent with benchmark
version or within acceptable standard
&pecial
$onsiderations:
0ot all properties for custom and third party objects can be accessed.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (-
Test Plan Guidelines
AQS
1-., Performance Profiling
["erformance profiling is a performance test in which response times, transaction rates, and other time
sensitive re!uirements are measured and evaluated. 'he goal of "erformance "rofiling is to verify
performance re!uirements have been achieved. "erformance profiling is implemented and executed to profile
and tune a target*of*test1s performance behaviors as a function of conditions such as wor0load or hardware
configurations.
23'%4 'ransactions below refer to 5logical business transactions.6 7or %.g. 'hese transactions are defined
as specific 'est cases that an user of the system is expected to perform using the target*of*test, such as add or
modify a given contract.]
Test Objective: /erify performance behaviours for desi!nated transactions or business
functions under the followin! conditions:
+ normal anticipated workload
+ anticipated worse case workload
Technique: 2se Test )rocedures developed for 3unction or 'usiness $ycle Testin!.
(odify data files "to increase the number of transactions# or the scripts to
increase the number of iterations each transaction occurs.
&cripts should be run on one machine "best case to benchmark sin!le user
sin!le transaction# and be repeated with multiple clients "virtual or actual
see special considerations below#.
$ompletion $riteria: &in!le Transaction - sin!le user: &uccessful completion of the test scripts
without any failures and within the e.pected - required time allocation "per
transaction#
(ultiple transactions - multiple users: &uccessful completion of the test
scripts without any failures and within acceptable time allocation.
&pecial
$onsiderations:
$omprehensive performance testin! includes havin! a 4back!round5
workload on the server.
There are several methods that can be used to perform this includin!:
4Drive transactions5 directly to the server usually in the form of &67 calls.
$reate 4virtual5 user load to simulate many "usually several hundred#
clients. 8emote Terminal Emulation tools are used to accomplish this load.
This technique can also be used to load the network with 4traffic.5
2se multiple physical clients each runnin! test scripts to place a load on the
system.
)erformance testin! should be performed on a dedicated machine or at a
dedicated time. This permits full control and accurate measurement.
The databases used for )erformance testin! should be either actual si*e or
scaled equally.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (8
Test Plan Guidelines
AQS
1-.- #oad Testing
[8oad testing is a performance test which subjects the target*of*test to varying wor0loads to measure and
evaluate the performance behaviors and ability of the target*of*test to continue to function properly under
these different wor0loads. 'he goal of load testing is to determine and ensure that the system functions
properly beyond the expected maximum wor0load. -dditionally, load testing evaluates the performance
characteristics #response times, transaction rates, and other time sensitive issues$.]
[23'%4 'ransactions below refer to 5logical business transactions.6 'hese transactions are defined as
specific functions that an end user of the system is expected to perform using the application, such as add or
modify a given contract.]
Test Objective: /erify performance behaviours time for desi!nated transactions or
business cases under varyin! workload conditions.
Technique: 2se tests developed for 3unction or 'usiness $ycle Testin!.
(odify data files "to increase the number of transactions# or the tests to
increase the number of times each transaction occurs.
$ompletion $riteria: (ultiple transactions - multiple users: &uccessful completion of the tests
without any failures and within acceptable time allocation.
&pecial
$onsiderations:
7oad testin! should be performed on a dedicated machine or at a
dedicated time. This permits full control and accurate measurement.
The databases used for load testin! should be either actual si*e or scaled
equally.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT (C
Test Plan Guidelines
AQS
1-.( 'tress Testing
[Stress testing is a type of performance test implemented and executed to find errors due to low resources or
competition for resources. 8ow memory or dis0 space may reveal defects in the target*of*test that aren1t
apparent under normal conditions. 3ther defects might results from competition for shared resource li0e
database loc0s or networ0 bandwidth. Stress testing can also be used to identify the pea0 wor0load the target*
of*test can handle.]
[23'%4 9eferences to transactions below refer to logical business transactions.]
Test Objective: /erify that the tar!et+of+test functions properly and without error under the
followin! stress conditions:
little or no memory available on the server "8%( and D%&D#
ma.imum "actual or physically capable# number of clients connected "or
simulated#
multiple users performin! the same transactions a!ainst the same data -
accounts
worst case transaction volume - mi. "see performance testin! above#.
0OTE&: The !oal of &tress test mi!ht also be stated as identify and document
the conditions under which the system 3%I7& to continue functionin!
properly.
&tress testin! of the client is described under section 9.:.:: $onfi!uration
testin!.
Technique: 2se tests developed for )erformance )rofilin! or 7oad Testin!.
To test limited resources tests should be run on sin!le machine 8%( and
D%&D on server should be reduced "or limited#.
3or remainin! stress tests multiple clients should be used either runnin! the
same tests or complementary tests to produce the worst case transaction
volume - mi..
$ompletion
$riteria:
%ll planned tests are e.ecuted and specified system limits are reached -
e.ceeded without the software or software failin! "or conditions under which
system failure occurs is outside of the specified conditions#.
&pecial
$onsiderations:
&tressin! the network may require network tools to load the network with
messa!es - packets.
The D%&D used for the system should temporarily be reduced to restrict the
available space for the database to !row.
&ynchronisation of the simultaneous clients accessin! of the same records -
data accounts.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 3&
Test Plan Guidelines
AQS
1-.. Volume Testing
[:olume 'esting subjects the target*of*test to large amounts of data to determine if limits are reached that
cause the software to fail. :olume testing also identifies the continuous maximum load or volume the target*of*
test can handle for a given period. 7or example, if the target*of*test is processing a set of database records to
generate a report, a :olume 'est would use a large test database and chec0 that the software behaved normally
and produced the correct report.]
Test Objective: /erify that the tar!et+of+test successfully functions under the followin! hi!h
volume scenarios:
ma.imum "actual or physically capable# number of clients connected "or
simulated# all performin! the same worst case "performance# business
function for an e.tended period.
ma.imum database si*e has been reached "actual or scaled# and multiple
queries - report transactions are e.ecuted simultaneously.
Technique: 2se tests developed for )erformance )rofilin! or 7oad Testin!.
(ultiple clients should be used either runnin! the same tests or
complementary tests to produce the worst+case transaction volume - mi. "see
stress test above# for an e.tended period.
(a.imum database si*e is created "actual scaled or filled with
representative data# and multiple clients used to run queries - report
transactions simultaneously for e.tended periods.
$ompletion
$riteria:
%ll planned tests have been e.ecuted and specified system limits are
reached - e.ceeded without the software or software failin!.
&pecial
$onsiderations:
1hat period of time would be considered an acceptable time for hi!h volume
conditions;
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 31
Test Plan Guidelines
AQS
1-./ 'ecurit8 and Access Control Testing
[Security and -ccess /ontrol 'esting focus on two 0ey areas of security4
-pplication*level security, including access to the )ata or usiness 7unctions, and
System*level Security, including logging into . remote access to the system.
-pplication*level security ensures that, based upon the desired security, ,sers are restricted to specific
functions . 'est cases or are limited in the data that is available to them. 7or example, everyone may be
permitted to enter data and create new accounts, but only managers can delete them. (f there is security at the
data level, testing ensures that user 5type6 one can see all customer information, including financial data,
however, user two only sees the demographic data for the same client.
System*level security ensures that only those ,sers granted access to the system are capable of accessing the
applications and only through the appropriate gateways.]
Test Objective: %pplication+level &ecurity: /erify that an user can access only
those functions - data for which their user type is provided
permissions.
&ystem+level &ecurity: /erify that only those 2sers with access to
the system and application"s# are permitted to access them.
Technique: %pplication+level: Identify and list each user type and the functions
- data each type has permissions for.
$reate tests for each user type and verify each permission by
creatin! transactions specific to each user.
(odify user type and re+run tests for same users. In each case
verify those additional functions - data are correctly available or
denied.
&ystem+level %ccess "see special considerations below#
$ompletion $riteria: 3or each known user type the appropriate function - data are
available and all transactions function as e.pected and run in prior
function tests
&pecial $onsiderations: %ccess to the system must be reviewed - discussed with the
appropriate network or systems administrator. This testin! may not
be required as it maybe a function of network or systems
administration.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 3(
Test Plan Guidelines
AQS
1-.2 4ailure 0 !eco"er8 Testing
[7ailure . 9ecovery testing ensures that the target*of*test can successfully fail and recover from a variety of
hardware, software, or networ0 malfunctions with undue loss of data or data integrity.
7ailure testing ensures that, for those systems that must be 0ept running, when a failure condition occurs, the
alternate or bac0up systems properly 5ta0e over6 for the failed system without loss of data or transactions.
9ecovery testing is an antagonistic test process in which the application or system is exposed to extreme
conditions #or simulated conditions$ to cause a failure, such as device (.3 failures or invalid database pointers
. 0eys. 9ecovery processes are invo0ed and the application . system is monitored and . or inspected to verify
proper application . system . and data recovery has been achieved.]
Test ObFect<eG %erf6 t"at reco<er6 processes J#an!al or a!to#ateDK properl6 restore
t"e Database9 applcatons9 anD s6ste# to a DesreD9 =noIn9 state. T"e
folloIn4 t6pes of conDtons are to be ncl!DeD n t"e testn4G
,oIer nterr!pton to t"e clent
,oIer nterr!pton to t"e ser<er
+o##!ncaton nterr!pton <a netIor= ser<erJsK
Interr!pton9 co##!ncaton9 or poIer loss to DA'D anD or
DA'D controllerJsK
Inco#plete c6cles JData flter processes nterr!pteD9 Data
s6nc"ronQaton processes nterr!pteDK.
In<alD Database ponter ? =e6s
In<alD ? corr!pteD Data ele#ent n Database
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 33
Test Plan Guidelines
AQS
Tec"n>!eG Tests createD for F!ncton anD 2!sness +6cle testn4 s"o!lD be !seD
to create a seres of transactons. Once t"e DesreD startn4 test pont s
reac"eD9 t"e folloIn4 actons s"o!lD be perfor#eD Jor s#!lateDK
nD<D!all6G
,oIer nterr!pton to t"e clentG poIer t"e ,+ DoIn
,oIer nterr!pton to t"e ser<erG s#!late or ntate poIer
DoIn proceD!res for t"e ser<er
Interr!pton <a netIor= ser<ersG s#!late or ntate
co##!ncaton loss It" t"e netIor= Jp"6scall6 Dsconnect
co##!ncaton Ires or poIer DoIn netIor= ser<erJsK ?
ro!tersK.
Interr!pton9 co##!ncaton9 or poIer loss to DA'D anD or
DA'D controllerJsKG s#!late or p"6scall6 el#nate
co##!ncaton It" one or #ore DA'D controllers or
De<ces.
Once t"e abo<e conDtons ? s#!lateD conDtons are ac"e<eD9
aDDtonal transactons s"o!lD exec!teD anD !pon reac"n4 t"s seconD
test pont state9 reco<er6 proceD!res s"o!lD be n<o=eD.
Testn4 for nco#plete c6cles !tlQes t"e sa#e tec"n>!e as DescrbeD
abo<e except t"at t"e Database processes t"e#sel<es s"o!lD be
aborteD or pre#at!rel6 ter#nateD.
Testn4 for t"e folloIn4 conDtons re>!res t"at a =noIn Database
state be ac"e<eD. 'e<eral Database felDs9 ponters anD =e6s s"o!lD
be corr!pteD #an!all6 anD Drectl6 It"n t"e Database J<a Database
toolsK. ADDtonal transactons s"o!lD be exec!teD !sn4 t"e tests fro#
Applcaton F!ncton anD 2!sness +6cle Testn4 anD f!ll c6cles
exec!teD.
+o#pleton +rteraG In all cases abo<e9 t"e applcaton9 Database9 anD s6ste# s"o!lD9 !pon
co#pleton of reco<er6 proceD!res9 ret!rn to a =noIn9 Desrable state.
T"s state ncl!Des Data corr!pton l#teD to t"e =noIn corr!pteD felDs9
ponters ? =e6s9 anD reports nDcatn4 t"e processes or transactons
t"at Iere not co#pleteD D!e to nterr!ptons.
'pecal +onsDeratonsG Reco<er6 testn4 s "4"l6 ntr!s<e. ,roceD!res to Dsconnect cabln4
Js#!latn4 poIer or co##!ncaton lossK #a6 not be Desrable or
feasble. Alternat<e #et"oDs9 s!c" as Da4nostc softIare tools #a6
be re>!reD.
Reso!rces fro# t"e '6ste#s Jor +o#p!ter OperatonsK9 Database9 anD
NetIor=n4 4ro!ps are re>!reD.
T"ese tests s"o!lD be r!n after "o!rs or on an solateD #ac"neJsK.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 3+
Test Plan Guidelines
AQS
1-.10 Configuration Testing
[/onfiguration testing verifies the operation of the target*of*test on different software and hardware
configurations. (n most production environments, the particular hardware specifications for the client
wor0stations, networ0 connections and database servers vary. /lient wor0stations may have different software
loaded #e.g. applications, drivers, etc.$ and at any one time many different combinations may be active and
using different resources.]
Test ObFect<eG %erf6 t"at t"e tar4et-of-test f!nctons properl6 on t"e re>!reD
"arDIare ? softIare conf4!ratons.
Tec"n>!eG /se F!ncton Test scrpts
Open ? close <aro!s non-tar4et-of-test relateD softIare9 s!c" as t"e
Mcrosoft applcatons9 Excel anD &orD9 et"er as part of t"e test or
pror to t"e start of t"e test.
Exec!te selecteD transactons to s#!late !serTs nteractn4 It" t"e
tar4et-of-test anD t"e non-tar4et-of-test softIare
Repeat t"e abo<e process9 #n#Qn4 t"e a<alable con<entonal
#e#or6 on t"e clent.
+o#pleton +rteraG For eac" co#bnaton of t"e tar4et-of-test anD non-tar4et-of-test
softIare9 all transactons are s!ccessf!ll6 co#pleteD It"o!t fal!re.
'pecal +onsDeratonsG &"at non-tar4et-of-test softIare s neeDeD s a<alable9 accessble
on t"e Des=topU
&"at applcatons are t6pcall6 !seDU
&"at Data are t"e applcatons r!nnn4 J.e. lar4e spreaDs"eet
openeD n Excel9 $CC pa4e Doc!#ent n &orDKU
T"e entre s6ste#s9 Net&are9 netIor= ser<ers9 Databases9 etc.
s"o!lD also be Doc!#enteD as part of t"s test.
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 3,
Test Plan Guidelines
AQS
1-.11 Installation Testing
[(nstallation testing has two purposes. 'he first is to insure that the software can be installed under different
conditions, such as a new installation, an upgrade, and a complete or custom installation, and under normal
and abnormal conditions. -bnormal conditions include insufficient dis0 space, lac0 of privilege to create
directories, etc. 'he second purpose is to verify that, once installed, the software operates correctly. 'his
usually means running a number of the tests that were developed for 7unction testing.]
Test ObFect<eG %erf6 t"at t"e tar4et-of-test properl6 nstalls onto eac" re>!reD
"arDIare conf4!raton9 !nDer t"e folloIn4 conDtons Jas re>!reDKG
NeI Installaton9 a neI #ac"ne9 ne<er nstalleD pre<o!sl6 It"
/pDate #ac"ne pre<o!sl6 nstalleD 9 sa#e <erson
/pDate #ac"ne pre<o!sl6 nstalleD 9 olDer <erson

Tec"n>!eG Man!all6 or De<elop a!to#ateD scrpts to <alDate t"e conDton of
t"e tar4et #ac"ne JneI - ne<er nstalleD9 sa#e <erson or olDer
<erson alreaD6 nstalleDK.
La!nc" ? perfor# nstallaton.
/sn4 a preDeter#neD s!b-set of f!ncton test scrpts9 r!n t"e
transactons.
+o#pleton +rteraG transactons exec!te s!ccessf!ll6 It"o!t fal!re.
'pecal +onsDeratonsG &"at transactons s"o!lD be selecteD to co#prse a confDence test
t"at applcaton "as been s!ccessf!ll6 nstalleD anD no #aFor
softIare co#ponents are #ssn4U
'e# No+ ,.-- . Release Date+ -,.,-./--, PA0A1S0T0TPT 36