Vous êtes sur la page 1sur 51

TESTING TOOLS

BY
N A G E S W A R R A O
TESTING TOOLS
1
Software Quality:
~ Meet Customer Requirements
~ Meet Customer Expectations (Speed of Processing Ease of !se"
~ Possi#le cost to Purc$ase
~ %ime to Mar&et

Software Pro'ect: ( ) set of customer requirements sol*ed #y people t$roug$ a
Software Engineering Processes is called Software Pro'ect+
Software Quality )ssurance: ( %$ese concepts are monitoring and measuring t$e
strengt$s of t$e de*elopment processes+
,-.E C/C,E %ES%-01: ( .-S2 M34E,
)nalysis 4esign Coding Maintenance
-nformation 5lac& 5ox %esting
1at$ering %ec$niques
Re*iews Re*iews 6$ite 5ox %est S7w C$anges
(Sen+ Soft (Sen+ Soft %esting
)nalyst" 4esigner" (Sen+ Soft
4e*elopers"
Common Software 4e*elopment Stages along wit$ ,ife Cycle %esting (,C%"
,C4: ( ,ife Cycle 4e*elopment
2,4: ( 2ig$ ,e*el 4esign 4ocument
,,4: ( ,ow ,e*el 4esign 4ocument
5RS: ( 5usiness Requirement Speci8cation
CRS: ( Customer Requirement Speci8cation
SRS: ( Software Requirement Speci8cation
Re*iew: ( %o *erify Correctness and Completeness of a document corresponding
people conduct Re*iews+
-t is a Static %esting %ec$nique
Prototype: ( ) sample model of an application to *erify Correctness and
Completeness of corresponding design documents+
5RS: ( Consists of Customer Requirements to ac$ie*e
S6RS: ( Software Requirement Speci8cation consists of functional and system
requirements to de*elop software wit$ respect to 5RS+
2,4: ( Consists of 3*erall 2ierarc$y of all t$e modules wit$ respect to required
functionalities+
,,4: ( Consists of -nternal ,ogic of e*ery Su# module in terms of Structural
,ogical and 4ata#ase (ER 4iagrams"+
6$ite 5ox %esting: ( ) Coding le*el testing conducted to *erify correctness and
completeness of programs+
2
5lac& 5ox %esting: ( %o *alidate customer expected requirements in a #uild
depends on external interface+
9eri8cation: ( 6$et$er t$e system is rig$t or wrong+
9aliditation: ( 6$et$er t$e system is rig$t system or not wit$ respect to customer
requirements+
5uild: ( ) 8nally integrated all module set wit$ respect to 2,4+
V-MODEL:-
9( Stands for *eri8cation and *alidation+ -t is an extension form of .is$ Model to de8ne
,ife Cycle 4e*elopment along wit$ ,ife Cycle %esting+
4e*elopment %esting
-7. 1at$ering : )nalysis ~ )ssessment of 4e*elopment Plan
~ Prepare %est Plan
~ Requirement P$ase %esting
4esign : Coding ~ 4esign P$ase %esting
~ Program P$ase %esting (65%"
-nstall 5uild ~ .unctional : System %esting (55%"
~ !ser )cceptance %esting
~ %est Management Processes
Maintenance ~ Port %esting
~ %est Software C$anges
~ %est E;ciency (4RE < )7)=5"
Defect Removal Efcienc: ( A ! A"B (Te#tin$ E;ciency"
6$ere ) > 4efects found #y %esting %eam during %esting+
6$ere 5 > 4efects found #y Customer side people during Maintenance+
-t is also &nown as 4efect 4e8ciency (5 ! A"B > Customer E;ciency"
~ %ime and Cost E?ecti*e is 4raw#ac& of 9(Model
~ Maximum will ac$ie*e quality software
Re%nement &o'm of V-Mo(el:(
5RS7CRS7!RS ((((((((((((((((((((((((((((((((((((((((((((( !ser )cceptance %esting
S6RS ((((((((((((((((((((((((((((((((((( .unctional and System %esting (55%"

2,4 (((((((((((((((((((((((((((( -ntegration %esting (65%"
(Com#ination of Modules"
3
,,4((((((((((((((((!nit %esting
Coding
.rom t$e a#o*e model small scale and medium scale Companies are maintaining
separate %esting %eam for functional and System %esting ,e*el+ Remaining Stages of
%esting done #y same 4e*elopment category People+
@ Te#tin$ Team:(
Quality Control (CE3" > )lmost Management 4e8ne %esting 1oals
Quality )nalyst (Pro'ect Manager" ( 4e8ne %est )pproac$ 7 Strategies : Met$olodigies
%est Manager > Sc$edule test approac$
%est ,ead > Maintenances %esting %eam wit$ respect to Plan
%est Engineer > Conduct testing to 8nd defects
-n small scale companies Quality )nalyst and %est Manager Responsi#ilities are $andled
#y Pro'ect Manager+
I) Revie*# (+'in$ Anal#i#:-
-n Software 4e*elopment ,ife Cycle 5usiness )nalyst Category people start
information gat$ering to de8ne customer requirement to resol*e+ -n t$is stage
5usiness de*elopment people after completion of 5RS (5usiness Requirement
Speci8cation" t$ey concentrate on re*iews of t$e document for completeness and
correctness+ )fter completion of t$ese re*iews t$ey de*elop S6RS (Software
Requirement Speci8cation" wit$ require .unctionality 4escriptions System
Requirements (2ardware and Software" to de*elop t$at functionality+ %o re*iew t$is SRS
4ocument t$ey concentrate on #elow questioner:
~ Meet Customer Requirements (Correctness"A
~ )re t$ey CompleteA
~ )re t$ey ac$ie*a#le (%ec$nology"A
~ )re t$ey Reasona#le (%ime and Cost"A
~ )re t$ey %esta#leA
II) Revie*# (+'in$ De#i$n:-
)fter Completion of )nalysis and Corresponding re*iews %ec$ ,eads (%ec$nical
Category people" concentrate on external and internal design of modules+ External
design de8nes 2ig$ ,e*el 4esign of all modules 2ierarc$y+ -nternal design de8nes
internal logic of e*ery su# module (Ex: Structural ,ogic (Program ,ogic" and 5ac&end
,ogic"+ )fter completion of de*elopment t$ey concentrate on Re*iews of t$at
document+ 4epends on #elow questioner:(
~ )re t$ey CompleteA
~ )re t$ey meet Customer RequirementsA
~ )re t$ey !nderstanda#leA
4
~ )re t$ey )c$ie*a#le (Coding"A
~ )re t$ey co*ers Error > 2andlingA
!SER -4 7 P)SS63R4
!SER ,31-0 -053B
-09),-4
III) ,nit Te#tin$:-
)fter completion of design documents and t$eir re*iews Programmers are
concentrating on coding for p$ysical design of software+ 4uring coding stage t$ey are
conducting !nit %esting at Program ,e*el or Module ,e*el+
~ Source code of program
~ )pply 6$ite 5ox %ec$niques
C" Execution %ec$niques :(
a" 5asis Pat$s Co*erage (Execute e*ery statement of program at least once"
#" ,oops Co*erage (%o 8nd c$ances of in8nite loops"
c" Program %ec$nique Co*erage (,ess num#er of Memory Cycles and CP! Cycles"
D" 3perations %esting:(
a" Run on Customer Expected Platforms (3S Compliers 5rowsers EE"
IV) Inte$'ation Te#tin$:-
)fter Completion of modules de*elopment and indi*idual testing de*elopment
people concentrate on Coupling (Com#ine" t$eir modules depends on 2,4 (2ig$ ,e*el
4esign 4ocument"+ 4uring t$is coupling of t$ese modules t$ey are conducting testing
(to *erify w$et$er all modules are correctly coupled or not"+
%3P > 4360 )PPR3)C2 53%%3M !P )PPR3)C2
M)-0 M)-0
S%!5 4R-9ER
Su# C Su# D Su# C
Su# D
S)046-%C2 %ES%-01
M)-0
5
4R-9ER
Su# C
S%!5
Su# D Su# F
Stu# is a called program+
4ri*er is a calling program
%op down )pproac$: ( Conducting testing on modules wit$ our coming to su# modules+
4ri*er: -t is a temporary program and it pro*ides a connection to su# module instead of
main module+
Stu#: -t is a temporary program and it sends #ac& control to main modules instead of
su# module+
Com#ination of %op down )pproac$ and 5ottom up )pproac$ is called Sand witc$
testing+
V) S#tem Te#tin$:-
~ Conducted #y Separate %esting %eam
~ 5uild le*el %esting
~ )pply 5lac& 5ox %esting %ec$niques to *alidate #uild wit$ respect to SRS+
%$is system testing classi8ed in to G categories:
C+ !sa#ility %esting
D+ .unctional %esting (4ynamic %esting"
F+ Performance %esting
G+ Security %esting
!sa#ility and .unctional %esting are Core (3#ligatory"
Performance and Security %esting are )d*anced (4epends on company en*ironment
and s&ill set of people"
-) ,#a.ilit Te#tin$: - In general a testing team starts system testing depends on
S6RS+ -n t$is testing process testing people concentrate on ease or use of
screens (!ser friendliness"+ %$is usa#ility testing di*ided into two su# le*els :
a/ ,#e' Inte'face Te#tin$ :- (Static %esting"
Ease of use: !nderstanda#le to operate
,oo& and .eel: Pleasantness
Speed in -nterface: ,ess num#er of e*ents to complete a tas&
H
./ Man+al S+00o't Te#tin$: - Correctness and completeness of user
manual de*eloped #y writer on $elp document+
!ser -nterface %esting (Early days of Io#"
!sa#ility %esting (Remaining System %esting"
6
Manuals support %esting (End days of Io#"
1) &+nctional Te#tin$: - In general %esting %eam spend more days of test duration
for functional testing to *alidate JMeet Customer RequirementsK+ -t consists of
#elow su#tests :
a/ .unctionality or Requirement %esting: ( 4uring t$is test %est Engineer
concentrate on correctness of e*ery functionality wit$ respect to S6RS+ -n
t$is test %est Engineer *eri8es #elow factors :
~ 5e$a*ioral C$ec& (3#'ect Properties 9ariations"
~ (-7P" -nput 4omain C$ec& (%ype and SiLe of o#'ect *alues"
~ Error > 2andling (Meaningful error messages to pre*ent negati*e
na*igations"
~ Calculations (Correct 3utput"
~ 5ac&end Co*erage (4ata 9alidations and 4ate -ntegrity"
~ Ser*ice ,e*els ( 3rder of .unctionalities"
~ Successful .unctionality (Com#ination of a#o*e all"
System %esting
MNO (((( .unctional %esting
MNO ((((( .unctionality7Requirements
./ -nput 4omain %esting :( 6$et$er our #uild input o#'ects are ta&ing rig$t
range and type of *alues or notA -t is a part of .unctionality7Requirement
%esting+
59) (5oundary 9alue )nalysis"
ECP (Equi*alence Class Portioning"
59) (Range7SiLe" ECP (%ype"
Min > Pass 9alid -n*alid
Max > Pass
Min(C > .ail Pass .ail
Min=C > Pass
Max(C > Pass
Max=C > .ail
Eg:( .rom .unctional Speci8cations our application allows !ser -4 and Passwords as
inputs to ,ogin+ !ser -d allows alp$a numeric from G to CP c$aracters long+ Password
allows alp$a#ets in lower case from G to M c$aracters long+
!SER -4 :( SiLe
59) (Range7SiLe" ECP (%ype"
Min > Pass ( G 9alid -n*alid
Max > Pass ( CP
Min(C > .ail ( F a(L Special c$aracters
Min=C > Pass ( Q )(R 5lan&
Max(C > Pass ( CQ N(S
7
Max=C > .ail ( CT Pass .ail
P)SS63R4 :( G(M (SiLe"
59) (Range7SiLe" ECP (%ype"
Min > Pass ( G 9alid -n*alid
Max > Pass ( M
Min(C > .ail ( F a(L Special c$aracters
Min=C > Pass ( Q )(R
Max(C > Pass ( T N(S
Max=C > .ail ( S
c/ Reco*ery %esting (Relia#ility %esting" :( 6$et$er your application c$ange
from a#normal state to normal state implicitly or notA
)#normal
5ac&up and Reco*ery Procedures
0ormal
Reco*ery %esting is an extensi*e form of Error > 2andling %esting+
(/ Compati#ility %esting :( 6$et$er your application run on customer
expected platforms or notA %$is testing is also &nown as Porta#ility
%esting+
Eg :( 6in 0% 6in BP (4epends on need of Customer"
95 > !0-B 3racle76indows SQ
5uild 3s 5uild 3s
.orward 5ac&ward
%$ese pro#lems we go t$roug$ w$en run on di?erent platforms+
%$ere are two types of compata#ility+ Suc$ as .orward Compati#ility and 5ac&ward
Compati#ility+
Eit$er .orward or 5ac&ward Compati#ility de*elopment team concentrate on c$anges
in 5uild+
e/ Compati#ility %esting: ( %$is testing is also &nown as 2ardware
Comapta#ility %esting+
Eg: ( Printer support
6$et$er your application #uild supports di?erent tec$nology $ardware
de*ices or notA
f/ -nter Systems %esting: ( 6$et$er your application #uild coexistence wit$
existing software in customer side to s$are resources or notA
8
%$is testing is also &nown as JEnd to End testingK+
System S7w ((((((((((((((( Compati#ility
2ardware ((((((((((((((( Con8guration
)pplication S7w (((((((((((( -nter System
$/ -nstallation %esting :(
5uild = Required -nstall Customer Site li&e Con8guration
S76 to Run 5uild
Setup program execution di?erent -nstallation+
Early -nterface during -nstallation+
3ccupied after -nstallation+
2/ -nter Systems %esting: ( %esting team conduct t$is test on #uild to 8nd
extra features 6it$ respect to SRS+ %$is testing is also &nown as
J1ar#age %estingK+
i/ Parallel %esting or Comparati*e %esting: ( %$is testing is applica#le to
software products (de*eloped depends on o*erall requirements in mar&et"+
4uring t$is test %est Engineer compare our application #uild wit$ old
*ersions of some application or similar type of products in mar&et to 8nd
strengt$s and wee& ness of our #uild+
F" Performance %esting: ( -t is an ad*anced testing tec$nique and expensi*e to apply+
4uring t$is test %esting %eam concentrate on Speed of Processing+
%$is testing tec$nique consists of #elow su#tests:
a" ,oad %esting:( Execution of our application under predetermined le*els of
resources and customer expected load to estimate performance is called
J,oad %estingK+ %$is is also &nown as JScala#ility %estingK+(0um#er of !sers"
#" Stress %esting :( Execution of our application under predetermined le*els of
resources and JPea& ,oadK to estimate performance is called JStress %estingK+
c" 4ata 9olume %esting: ( %o 8nd 4ata 9olume limit $andled #y our #uild testing
team conducts t$is *olume testing+
-n terms of records+ (2ow muc$ amount of data your application $andles in
maximum+
Eg: ( Ms )ccess supports up to D15 limit+
d" Storage %esting: ( %o 8nd Storage *olume to $andle #y our #uild conducts t$is
testing+
-n terms of #ytes+
G" Security %esting: ( -t is an ad*anced testing tec$nique and
expensi*e+ 4uring t$is test testing team concentrate on JPri*acy
(Production" to user operations+
)ut$oriLation
)ccess Control ((((((((( .unctionality %esting
Encryption and 4ecryption ((((((( 5y 4e*eloper
Client Ser*er
Encrypt 4ecrypt
Eg: ( R)S Pu#lic Encryption
9
9- !ser )cceptance %esting: ( )fter completion of system testing our organiLation
team concentrate on user acceptance testing to collect feed#ac& from customer side
people+ %$ere are two types of user acceptance+
)lp$a %est 5eta %est
.or Software application .or Software Products
-n 4e*elopment Site -n customer Site li&e
9irtual En*ironment Real En*ironment
Collect .eed 5ac&
Quality
,C4 ,C%
)nalysis Re*iews
4esign Re*iews : Prototype
Coding !nit : -ntegration
System %esting(((((
!sa#ility
.unctional
Performance
Security
)lp$a
!ser )cceptance %esting
5eta
9-- %esting during Maintenance: ( )fter completion of user )cceptance le*el
*alidation our organiLation management concentrate on Release %eam .ormation+ %$e
8rst responsi#ility of Release %eam is JPort %estingK in customer side+ 4uring t$is
release team concentrate on #elow factors:
~ Compact -nstallation (.ull -nstallation"
~ 3*erall .unctionality (.irst to ,ast"
~ Uey#oard 2andling (-nput de*ices cooperation"
~ %erminal 2andling (Printer Scanner Monitor"
~ 3S Error > 2andling (Cooperation of Software )pplication and 3S"
~ Co Existence wit$ ot$er Software ()pplication wit$ ot$er software"
~ Support Secondary Storage 4e*ices (.loppy and C4"
)fter completion of JP3R% %ES%-01K release team concentrate on JE04 !SERVS
%R)-0-01K+
4uring utiliLation t$at software #y customer side people t$ey are sending
JC$ange RequestsK to our company+ %o $andle t$is c$ange requests our organiLation
maintains JCC5 (C$ange Control 5oard" w$ic$ consists of few de*elopers and testers+
C$ange Requests
En$ancement Missed 3#'ect
10
-mpact )nalysis -mpact )nalysis
Perform t$at c$ange Perform t$at c$ange
%est t$at c$ange Perform c$ange test process
%est t$at c$ange request c$ange
TESTING TERMINOLOGY
-) Mon3e Te#tin$ 4o'/ 52im0an6ee Te#tin$: - Co*erage of main acti*ities
during testing is called JMon&ey %estingK+
1 E70lo'ato' Te#tin$ 8:- ,e*el #y le*el of acti*ities (functionality" co*erage is
called JExploratory %estingK+
E$: ( 1olf game
9) Sanity %esting or %ester )cceptance %esting: ( 6$et$er 5uild is sta#le for
complete testing or notA %$is testing is also &nown as J%ester )cceptance
%estingK+
4e*elopment Release 5uild
Sanity %esting 7 Smo&e %esting 7 %ester )cceptance %esting
System %esting
!ser )cceptance %esting
:) Smo&e %esting: ( ) small S$a&eup in Sanity %esting is called JSmo&e %estingK+
4uring t$is test %ester estimates sta#ility of #uild wit$ reasons to do complete
testing+
;) 5ig #ang %esting: ( Conduct testing after completion of entire de*elopment of
software is called J5ig #ang %estingK+ -t is also &nown as J-nformal %estingK+
<) -ncremental %esting: ( ) multiple stages of testing are called J-ncremental
%estingK+ %$is testing is also &nown as J.ormal %estingK+
Eg: ( ,C% (,ife Cycle %esting"
=) Static %esting: ( Conduct a test wit$out running application is called JStatic
%estingK+
Eg: ( !ser -nterface %esting
>) 4ynamic %esting: ( Conduct a test t$roug$ running a #uild is called 4ynamic
%esting+
Eg: ( .unctionality ,oad Stress Compati#ility testing+
?) Manual *ersus )utomation: ( ) tester conducts a test on t$e #uild wit$out using
any t$ird party testing tool+ %$is style of test execution is called JManual
%estingK+
Eg: ( !ser -nterface testing
) tester conducts a test wit$ t$e $elp of a software testing tool+ %$is style of
test execution is called J%est )utomationK+
11
GNO
-mpact and Criticality
)utomation
Manual
-mpact indicates reputation (reusa#ility" in testing+
Criticality indicates complex to apply t$e test manually+
Eg: ,oad %est (CNNN computers"
-@) Retesting: ( Re execution of our test on same application #uild wit$
multiple input *alues is called JRetestingK+
-7pC %est 4ata
Min min
Min max
Max max
-7pD (*e =*e
=*e (*e
3U (*e (*e
Result *alue N
N *alue
N N
Expected: Result < i7pC W i7pD
--) Regression %esting: ( Re execution of our test on modi8ed #uild to ensure
#ug 8xes wor& and occurrence of side e?ects+
%est Related Passed %ests
.ailed
5uild Modi8ed 5uild
Passed
.ailed 4e*elopment
0ote: ( Retesting on same #uild
Regression testing on modi8ed #uild (((( #ot$ indicates %est reputation+
-mpact ((( Retesting Regression
Criticality ((( ,oad %esting and Stress %esting
Selection of )utomation (5y Quality )nalyst or Pro'ect Manager"X(
%$e need of automation for one pro'ect analyLed #y Quality )nalyst or Pro'ect
Manager depends on #elow factors+
C+ %ype of External -nterface:(
1!- (1rap$ical !ser -nterface" ( Suita#le
C!- (C$aracter !sed -nterface" > 0ot Suita#le
D+ SiLe of -nterface:(
12
2uge > 0eeded ()utomation"
,ess amount of screen > 0o need
F+ Expected num#er of releases:(
Expecting > 0eeded
4oesnVt Expect > 0o need
Eg: 9ersions in future En$ancement .uture Requirement
G+ Expected Maturity in future Releases:(
6in SQ( )utomation
6in SM > MNO = DNO new E+ ,ess maturity needed
6in SM ((( )utomation
6in 0% ((( DNO = MNO E new E $uge maturity expecting E no need
Q+ %est E;ciency: ( Unowledge of test automation of test engineers+
P+ Support from Management: ( %o #uy Software Management )ppro*al+
WIN R,NNER =)@
~ 4e*eloped #y Mercury -nteracti*e
~ .unctionality %esting %ools
~ Supports Client 7 Ser*er and 6e# %ec$nology suc$ as: 95 9C== )cti*e B
4DU 2%M, I)9) Power 5uilder 4elp$i Sie#el (ERP %ec$nology"+
~ %o support +0et BM, S)P PeopleSoft Multimedia 3racle )pplicationsE Etc+
we can use Q%P (Quic& %est Professional" extension of 6in Runner+
~ Run on 6indows (SQ SM 0% BP Ser*er"
~ %o conduct functionality testing in !0-B or ,-0!B we can use JB RunnerK+
~ Records our manual test processes in %S, (%est Script ,anguage" li&e as JCK
+
6in Runner %esting Processes:(
,earning
Recording
Edit Script
Run Script
)nalyLe Results
,earning: ( ReorganiLation (Mapping" of o#'ects and windows in your application
#y 6in Runner is called J,earningK+
13
6in Runner 5uild
,earning
Recording: ( ) test engineer records a manual test processes in J%S,K wit$
respect JRetesting and Regression %estingK+ (-mpact and Criticality"
Edit Script: ( )fter completion of a repeata#le manual test recording a test
engineer inserts our own statements to increase test e?orts+
Eg :( ,oop C$ec&points if Condition
Run Script: ( %est Engineer execute t$at test in required time and decide t$at test
is JP)SS or .)-,K+
)nalyLe Results: ( )fter %est execution 6in Runner returns results and t$ey are
analyLed #y %est Engineer to concentrate on J4efect ,ac&ingK+

,ogin Manual Procedure
!-4 .ocus to 6indow > 3U disa#led
P64 Enter !-4 > 3U disa#led
3U and Enter P64 > 3U ena#led
Expected: ( J3UK ena#led after enter !-4 and P64+
Start Recording %est Script:(
SetYwindow (JloginK F"X
5uttonYc$ec&Yinfo (Jo&K Jena#ledK N"X
EditYset (J!-4K JxxxK"X
5uttonYc$ec&Yinfo (Jo&K Jena#ledK N"X
PasswordYeditYset (JP64K JEncrypted PwdK"X
5uttonYc$ec&Yinfo (Jo&K Jena#ledK C"X
5uttonYpress (Jo&K"X
%est Script: ( )utomation programs or &nown as J%est ScriptK+ %$ey consist of two
types of statements Suc$ as:
C+ 0a*igational Statements
D+ C$ec& Points+
FC7CN7NG
)dd(-n Manager: ( %$is window pro*ides list of 6in Runner supported
tec$nologies depends on our current licenses ()cti*e B Power 5uilder 9isual
5asic and 6e# %est"
6in Runner Sym#ols:(
Start Recording
Run .rom %op
Run .rom point7arrow
Stop Recording
14
Pause (Ctrl=.F"
Recording Modes: ( %o automate our manual #usiness (test" operations on your
pro'ect (application #uild" we can use Jtwo modesK in 6in RunnerK+
a" Context Sensiti*e Mode
#" )nalog Mode
-n a#o*e two modes context sensiti*e mode is default+
a" Context Sensiti*e Mode: ( -t is an intelligent mode in 6in Runner+ -n t$is mode
6in Runner records our all mouse and &ey#oard operations on our application
#uild+
Eg: ( C" .ocus to window >
SetYwindow (Jwindow nameK time to focus"X
D" 5uttonYpress (
#uttonYpress (Jo&K"X
F" Select option in menu (
MenuYselectYitem (Jmenu nameX option nameK"X
G" Select a Radio #utton > 3n 73?
#uttonYset (Jradio #utton name: 30"X
%S, is a case sensiti*e language and maintains scripting in lower case and
corresponding .lags in !pper Case+
Q" C$ec& 5ox (
#uttonYset (Jc$ec& #ox nameK 30"X
P" Com#o 5ox 7 ,ist 5ox (
listYselectYitem (Jlist #ox nameK Jselect itemK"X
T" %ype text into edit #ox >
editYset (Jedit #ox nameK Jtyped textK"X
M" Password %ext 5ox >
passwordYeditYset (JP64 o#'ectK JEncrypted P64K"X
#" )nalog Mode: ( -n context sensiti*e mode 6in Runner records &ey#oard and
mouse operations only+ %o record mouse pointer moments %est Engineer use
analog mode in automation+
Eg: ( 4igital Signatures (E(5an&ing" 1rap$s 4rawing and -mage moments+
%o start recording in )nalog mode we can follow #elow na*igation+
Create Menu
Z
Record )nalog (.D"
-n t$is )nalog mode 6in Runner records mouse pointer moments wit$ respect to
des&top coordinates+ -n context sensiti*e mode 6in Runner records mouse operations
and &ey#oard operations wit$ respect to o#'ects and windows+
0ote:( %o c$ange from one mode to ot$er mode during recording %est Engineer
use J.DK as s$ortcut (or" Reclic& JStart RecordingK #utton+
0ote: ( 6e are getting wrong results wit$ analog mode script w$en monitor
resolution is c$ange or application poison c$anged+
15
CT7CN7NG
!ser 4e8ned .unctions: ( ,i&e as programming languages 6in Runner also allows
you to create !ser 4e8ned .unctions
%est Engineer uses t$is concept to record repeata#le na*igations in your
pro'ect+
!ser 4e8ne .unction
Compose Reply .orward 3pen
%est Scripts
.rom t$e a#o*e example %est Engineer are using !ser 4e8ned .unctions wit$
repeata#le na*igations as content wit$out any c$ec& points+
Syntax:(
Pu#lic7static function name (in7out7inout orgE"
[
Z
Z @ Repeata#le 0a*igation
Z
return(":
\
Pu#lic: ( ) function is accessi#le in any test
Static: ( ) function is accessi#le in any test #ut it maintains constant locations to
*aria#les w$en you are in*o&ing more t$an one times+
-n static functions tester maintains output state of one time execution as
input state for next+
-n: ( t$ese parameters are wor&ing as general arguments
3ut: ( t$ese parameters are wor&ing as return *alues+
-n3ut: ( t$ese parameters are wor&ing as #ot$+
Return(":( %ester uses t$is statement to return one *alue+
ExC+
Pu#lic function add (in a in # out c"
[
c<a=#X
\
Callin %est:(
x<CNX y<DNX
)dd (x y L"X
printf(L"
WWW EgX ( s=Hyderabad
s1=cyb
p=1
-- s=cyberabad
16
Prepare a User Defned function replace substring in main string position
in specifed position
Pu#lic function replaces (inout s in sC in p"
[
s<su#str (s C p(C":sC: su#str(sp= lengt$ (sC" lengt$ (s"X
s<K2ydera#adK
sC<Kcy#K
p<C
s<cy#:era#ad
<cy#era#ad
CM7CN7NG
.unction 1enerator:(
,i&e as 5uild in functions %est Engineer is adding !ser 4e8ned .unction names to
.unction generator wit$ required description and syntax+
%o do t$is tas& we can use #elow %S, .unctions:
C" 1eneratorYaddYcategory (Jcategory nameKX
(Pro'ect name is maintained as Category name:
D" generatorYaddYfunction (":( 6e can use t$is function to add !ser 4e8ned
.unction name to all function category+
Syntax: generatorYaddYfunction(Jfunction nameK JdescriptionK arity
Jarguments nameK Jargument typeK Jdefault *alueK E++ " [0um#er of
arguments\
1eneratorYaddYfunction (JfunK descriptionK F
JaK J#rowse ("K J J
J#K JpointYwindowK J J
JcK JpointYo#'ectK J J
JdK JselectYlist (N C D F G Q"K JNK
JeK JtypeYeditK J J"X
F" generatorYaddYfuctionYtoYcategory (Jcategory nameK Jfunction nameK"X
0ote: ( 6in Runner allows you to add our function name to our own category
w$en t$at function name is a*aila#le in all function categories+
,earning: ( ReorganiLation of o#'ects and windows in your application #y testing
tool is called J,earningK+
6in Runner T+N pro*ides J)uto ,earningK and JPre ,earningK+
-+ )uto ,earning:(
6in Runner 5uild
5uttonYpress(Jo&K"X 3U
,ogical name:o&
[
17
class<pus$ #utton
la#el<Ko&K
\
ReorganiLation of o#'ects and windows in your application #y testing tool
during recording is called J)uto ,earningK+
StepC: Start Recording
StepD: RecogniLe o#'ect
StepF: Script 1eneration
StepG: Catc$ entry
StepQ: Catc$ o#'ect
.rom t$e a#o*e model a reorganiLation entry of any o#'ect consists of two parts:
,ogical name > to use in script and p$ysical description to catc$ o#'ect+
%o edit t$ese entries we can use
%ools menu
Z
1!- Map Editor
1!- Map editor maintenance reorganiLation of entries of o#'ects and windows+ %o
$andle t$ese entries %est Engineer follows two types of modes
a" 1lo#al 1!- Map .ile
#" Per %est Mode (0ew concept in 6in Runner T+N"
-n a#o*e modes 6in Runner maintains 1lo#al 1!- Map 8le concept as default+
CS7CC7NG
)" 1lo#al 1!- Map .ile: ( -n t$is mode 6in Runner maintains common entries or o#'ects
and windows w$en t$ey participate in more t$an test script+
%est C
%est D 1!- Map Sa*e73pen 1!-
(244"
%est F Explicitly
.rom t$e a#o*e model test engineer sa*e t$at entries and open t$at entries
using 8le menu in 1!- map editor+
-f you forget entries sa*ing 6in Runner maintains entries into #u?er #y default+
Eg:( ,N > CNU5 ,C ((( CN U5 <<<<<<< %emporary 5u?er
-f you want to see t$ese #u?er entries we can follow #elow na*igation+
%ools
Z
1!- Map editor
Z
9iew Menu
Z
1!- .iles
Z
18
,N %emporary
,C %emporary
#" Per %est Mode: ( -t is a new concept in 6in Runner T+N+ -n t$is mode 6in Runner
maintains entries into 2ard dis& t$roug$ auto processes+
%est C +gui
Sa*e 7 3pen
1!- Map
%est D -mplicitly +gui
5y 4efault 6in Runner maintains 1lo#al 1ui Map 8le+ -f you want to c$ange to per test
mode we can follow #elow na*igation+
Setting menu
Z
1eneral 3ptions
Z
En*ironmental %a#
Z
Select 1!- Map 8les per test
Z
Clic& )pply
Z
Clic& 3&
--+ Pre ,earning :( 6in Runner T+N and lower *ersions supports resignation of o#'ects
and windows #efore starting recording+ %$is type of learning is called JPre ,earningK+
%o conduct t$is pre learning we can use JRapid %est Script 6iLardK (R%S6" in
Create Menu+
0a*igation:(
Create Menu
Z
R%S6
Z
Clic& 0ext
Z
S$ow application main window
Z
Clic& 0ext
Z
Select 0o test
Z
Clic& 0ext
Z
Enter Su# menu Sym#ols
Z
Clic& 0ext
Z
Select Pre ,earning Mode
19
[Express > continuous\
[Compre$ensi*e > Stop and .orward\
Z
Clic& ,earn
Z
[)fter ,earning\
Say /es 7 0o
[%o open your pro'ect during 6in Runner ,aunc$ing\
Z
Clic& next
Z
Remem#er t$e pat$ of startup script and 1!- Map .ile
Z
Clic& 0ext
Z
Clic& 3&
1!-Y,oad (":( 6in Runner use t$is function to load 1!- Map 8le into a 1!- Map+
Syntax: ( 1!-Yload (Jpat$ of 1!- Map .ileK"
)uto ,earning Pre ,earning
4uring Recording #efore Recording
0o need of extra 0a*igation !sing R%S6
Entries maintain in D ways 3nly 1lo#al 1!- Map .ile
( 1lo#al 1ui Map .ile
( Per %est mode
4uring 6in Runner test )utomation %est Engineer perform c$anges in test scripts
and also perform c$anges in recognisation entries of o#'ects and windows+
C" 6ild Cord C$aracters (] W " :(

Some times your application window la#els are c$anging depends on
input *alues+ %o create data dri*en test on t$is type of windows we can perform
c$anges in 1!- Map editor entry of t$at window+
3R1-0),
,ogical 0ame: .ax order 0o+C
[
Class : 6indow
,a#el : J.ax order no+CK
\
M34-.-E4
,ogical 0ame: .ax order 0o+C
[
Class : 6indow
,a#el : J] .ax order no+WK
\
20
0a*igation:(
%ools
Z
1!- Map Editor
Z
Select required entry
Z
Clic& Modify
Z
C$ange p$ysical description wit$ wild cord c$aracters
Z
Clic& 3&
DC7CC7NG
D" Regular Expression: ( Some times in our application #uild o#'ect la#els are *ariation
due to e*ents+
,i&e as %oggle o#'ects in 95 > 30 7 3..
Eg: ( 3R1-0),
Start 7 Stop
,ogical 0ame: Start
[
Class : Pus$ 5utton
,a#el : J StartK
\
RE1!,)R EBPRESS-30
,ogical 0ame: Start
[
Class : Pus$ 5utton
,a#el : J ^s_ ^t_ ^ao_ ^a(L_K
\
G" 1ui Map con8guration: ( -n 6in Runner a test engineer faces a distinguis$a#le
pro#lem of o#'ects w$en t$ey consist of some p$ysical description wit$ respect
to 6in Runner default (class la#el"+ %o c$ange de8nition of p$ysical descript ^ton
we can follow #elow na*igation+
3U 3U
0a*igation:(
%ools
Z
1!- Map Con8guration
Z
Select o#'ect type
Z
Clic& Con8gure
Z
21
Select required properties into o#ligatory (default" and
optional (required time appears"
Z
Clic& 3&
,ogical name: 3U
[
Class: Pus$ 5utton
,a#el: J3UV
MS6-4: BBBB
\
,ogical name: 3U
[
Class: Pus$ 5utton
,a#el: J3UV
MS6-4: BBBBB
\
.rom t$e a#o*e example to distinguis$ more t$an one o#'ect 6in Runner
depends on o#ligatory properties as default and optional properties if required+
0ote: ( -n general 6in Runner maintains MS6-4 as optional property+ %$is
property pro*ides unique *alue to e*ery o#'ect+
Q" Mapped to Standard Class: ( Some times 6in Runner doesnVt pro*ides all
testa#le properties for required o#'ects+ %o get required testa#le properties for
t$at o#'ects we can follow #elow na*igation+
0a*igation:(
%ools
Z
1!- Map Con8guration
Z
Clic& )dd
Z
Select t$at non testa#le o#'ect
Z
Clic& o&
Z
Clic& con8gure
Z
Select Mapped to class
Z
Clic& 3&
Q" 9irtual 3#'ect 6iLard: ( 6e can use t$is option in 6in Runner to recogniLe non
recogniLed o#'ects forci#ly+
22
0a*igation:(
%ools
Z
9irtual 3#'ect 6iLard
Z
Clic& 0ext
Z
Select Expected %ype
Z
Clic& 0ext
Z
Mar& t$an non recogniLed o#'ect
Z
Rig$t clic& to lea*e
Z
Clic& 0ext
Z
Enter ,ogical name to new entry
Z
Say /es 7 0o to create more
Z
Clic& .inis$
P" Selecti*e Recording: ( -t is a new concept in 6in Runner T+N+ 6e can use t$is run
time setting to record our #usiness operations on speci8ed applications only+
0a*igation:(
Settings
Z
1eneral 3ptions
Z
Record %a#
Z
Clic& Selecti*e Recording
Record only selected applications
Z
Record on start menu and windows explorer
Z
5rowse your #uild +exe
Z
Clic& o&
!ser -nterface %esting: ( 6in Runner is a functionality testing tool+ 5ut it pro*ides a
faculty to conduct J!ser -nterface %estingK+
4uring t$is !ser -nterface %est 6in Runner depends on JMicrosoft S-B factorsK+
C" Controls are initial
D" 3U 7 Cancel existence
F" System menu existence
G" Controls are must *isi#le (`` aa"
Q" Controls are not o*erlapped
P" Controls are aligned
23
0a*igation:(
3pen 5uild
Z
Create Menu
Z
R%S6
Z
Clic& next
Z
S$ow application main window
Z
Select !ser -nterface test
Z
Clic& 0ext
Z
Specify su# menu sym#ols
Z
Clic& 0ext
Z
Specify learning mode
(Express 7 Compre$ensi*e"
Z
Clic& ,earn
Z
Say /es 7 0o to open your pro'ect automatically
Z
Remem#er t$e pat$s of startup script and 1!- map 8les
Z
Remem#er t$e pat$ of !ser -nterface test
Z
Clic& 3&
Z
Clic& Run
Z
)nalyLe Results manually
DD7CC7NG
%o conduct !ser -nterface testing on our application #uild using JMicrosoft P
RulesK 6in Runner pro*ides a system de8ned compiled module functions+
C:bProgram .ilesbMercury -nteracti*eb6in Runnerb,i#rarybc$&ui
,oadYosYapi (" (3s( 3perating System api ( )pplication
[
((
(((
\
24
Con8gureYc$&ui (YYYYYY"
[
((
(((
\
C$ec&Yui (Jwindow nameK"
[
((
(((
\
Ex:(
,oad (Jc$&uiK C C"X @ load required statements into R)M
,oadYosYapi ("X @ to acti*ate os system calls
t<get*ar (JtimeoutK"X
a < %R!EX @ initcap
# < .),SEX @ o&7cancel
c < %R!EX @ System Menu
d < %R!EX @ 9isi#le
e < .),SEX @ 0ot o*erlapped
f < %R!EX @ )lignment
con8gureYc$&ui (a#cdef"X
winYopen (JxK t"X
c$ec&Yui (JxK"X
winYclose (JxK"X
f < .),SEX @ alignment
con8gureYc$&ui (a#cdef"X @ to select required rules for test
winYopen (JyKt"X
c$ec&Yui (JyK"X @ to apply selected rules on speci8ed window
winYclose (JyK"X
Regression %esting :( 4uring JRegression %estingK to ensure 5ug 8x wor& and
occurrences of side e?ects %est Engineer perform multiple le*els of regression
testing+
C+ Recei*e modi8ed #uild from de*elopment team
D+ 1!- regression test
F+ 5itmap regression test ( %o 8nd screen le*el di?erences in(#etween old and new
#uild+
G+ Real regression test to ensure t$at modi8cation
C+ 1!- Regression %est:(
3,4 0E6
1!- C$ec& point
25
.rom t$e a#o*e model test engineer conducts 1!- regression test t$roug$
parallel testing tec$nique as manual+ %o automate t$is test we can follow #elow
na*igation+
Create Menu
Z
R%S6
(Rapid %est Script 6iLard"
Z
Clic& 0ext
Z
S$ow application main window
Z
Clic& next
Z
Select 1!- regression test
Z
Clic& next
Z
Enter su#menu sym#ols (E `` aa"
Z
Specify ,earning Mode
(Express and compre$ensi*e"
Z
Clic& ,earn
Z
Say /es 7 0o to open your application during 6in Runner launc$ing
Z
Remem#er t$e pat$ of startup script and 1!- map 8le
Z
Remem#er t$e pat$ of 1!- Regression test
Z
Clic& o&
Z
Close old 5uild
Z
3pen modi8ed #uild
Z
Clic& run
Z
)nalyLe results manually
D+ 5itmap Regression %est:(
3,4 0E6
5itmap C$ec& point
0a*igation li&e as a#o*e
Exception 2andling:(
Exception indicates a reco*era#le runtime error+ %o $andle t$ese exceptions test
engineer use required $andler functions+
26
6in Runner allows you to create F types of exceptions:
C+ %S, exceptions
D+ 3#'ect exceptions
F+ Pop up exceptions
C+ %S, Exceptions: ( %$ese exceptions rose w$en speci8ed %S, functions returns
speci8ed error+
(((( EY03%Y.3!04 ((((
(((( 2ow to open new sample window
((((
EY3U SetYwindow(JsampleK Q"X
(((( 2andler
((((
%est Script
0a*igation:(
%ools
Z
Exception $andling
Z
Select exceptions type as %S,
Z
Clic& 0ew
Z
Enter exception name
Z
Select required function name in list
Z
Select return code
Z
Enter $andler function name
Z
Clic& o&
Z
Clic& paste
Z
Clic& o& after reading suggestion
Z
Clic& close
Z
Record 2andler function #ody to reco*er t$at situation
Z
Ma&e it as compiled module
Z
6rite load statement in startup script of 6in Runner
Eg:(
Pu#lic function mindC (in rc in func"
[
printf (func :KreturnK : rc"X
\
27
D" 3#'ect Exceptions: ( %$ese Exceptions are raised w$en speci8ed o#'ect property is
equal to our expected+
4own %est Script
2andler (((( ena#led
[
(((
((( Re esta#lis$ connection
((((
\
0a*igation:(
%ools
Z
Exception $andling
Z
Select exception type as o#'ect
Z
Clic& 0ew
Z
Enter exception name
Z
Select 3#'ect
Z
Select required property wit$ expected
Z
Enter $andler function name
Z
Clic& o&
Z
Clic& Paste
Z
Clic& o& after reading suggestion
Z
Clic& close
Z
Record our required na*igation to reco*er t$at situation
Z
Ma&e it as complied module
Z
6rite load statement in startup script of 6in Runner
0ote: ( 3#'ect exceptions are used to maintain trace o#'ect states+
c" Pop up Exceptions: ( %o s&ip !0 wanted windows during test execution on our #uild
we can use pop up exceptions+
0a*igation:(
%ools
28
Z
Exception $andling
Z
Select exception type as pop up
Z
Clic& 0ew
Z
Enter Exception name
Z
Select 6indow
Z
Specify 2andler action
(Press Enter Clic& Cancel Clic& 3& !ser 4e8ned .unction"
Z
Clic& 3&
%o $andle t$ese exceptions long time during our test execution we can #elow
%S, statements+
ExceptionYo? (Jexception nameK"X
ExceptionYo?Yall ( "X
ExceptionYon (Jexception nameK"X
Exceptions: EC
ED
EF
EG
%est C %est D
ExceptionYo?Yall ("X ExceptionYo?Yall ("X
ExceptionYon (JeCK" ExceptionYon (JeFK"
ExceptionYon (JeDK" ExceptionYon (JeGK"
(((((((( ((((((((
(((((((( ((((((((
(((((((( ((((((((
6e# %esting: ( 6in Runner is a functionality testing tool and it pro*ides a set of facilities
to conduct functionality on we# interfaces (2%M,"+
Client Ser*er
Monitoring 4ata Storage
Manipulations
.at (More" %$in (,ess"
29
95 9C== Ia*a 4D& 9#+net MS )ccess 3racle SQ, Ser*er Sy#ase
D %ier )rc$itecture
5rowser 6e# Ser*er 4ata#ase
ser*er
2%M, 42%M, BM, %CP 7 -P ISP )SP Ia*a ser*lets 95 script
3racle SQ,
Ia*a Script Pearl cold .usion Ia*a Script ser*er
P2P
Monitoring Manipulation 4ata Storage
3 %ier )rc$itecture
4epends on a#o*e model a functionality %est Engineer applies #elow su# tests
on 6e# %ec$nologies+
C" 5e$a*ioral C$ec&ing
D" -nput 4omain Co*erage (!-4 7 P64"
F" Error > $andling (Client *alidation and ser*er *alidations"
G" Calculation Co*erage
Q" 5ac&end Co*erage (4ata *alidation and 4ata -ntegrity"
WP" !R,Vs (!niform Resource ,ocator" co*erage
WT" Static %ext Co*erage
M" Success functionality (Com#ination of a#o*e"
-n a#o*e possi#le functionality test !R,Vs testing and Static %est co*erage are
new topics to apply+
C" !R,Vs %esting (!niform Resource ,ocator":(
%$is test is also &nown as na*igational testing of we# pages #ecause we#
applications are lin&s dri*en applications+
4uring t$is test %est Engineer *alidates e*ery lin& in terms of lin&s Execution
and lin& existence+
,in& Execution indicates correctness of ext page occurrence+
,in& Existence indicates w$et$er t$e lin& is in rig$t place or notA
6in Runner allows you to automate a#o*e !R,Vs testing using 1!- C$ec& Point
on test lin&s image lin& cell ta#le and frame in we# pages+
DG7CC7NG
a" %est ,in&: ( -t is a non standard o#'ect and it consists of a set of non standard
properties+
0ote: ( %o automate 6e# functionality testing we can select we# test option in
)dd > -n Manager+
@ #ac& ground Color (@$exadecimal num#er of expected color"
W@ 5ro&en lin& (*alid 7 not *alid" (w$et$er t$e corresponding lin& pro*ides lin& in
separate window"
30
@ Color (@ $exadecimal"
@ .ont (Expected style"
@ %ext (Corresponding lin& text"
W@ !R, (expected pat$ of next page w$en you clic& t$at lin&"
Syntax:(
3#'Yc$ec&Ygui (Jlin& textK Jc$ec& list 8le name +c&lK Jexpected *alues 8leK
time to create "X
%o conduct a#o*e lin& !R,Vs testing test engineer collects required information
from de*elopment team called JSite Map 4ocumentK+
,in& name Expected !R,
WWWWWWW WWWWWWWW
WWWWWWW WWWWWWWW
WWWWWWW WWWWWWWW
WWWWWWW WWWWWWWW
%$is document pro*ides mapping #etween lin& name and expected !R, in ocine+
,ocal $ost Ser*er $ttp:77ser*ername7*dir7page name+$tml
%CP 7-P 3..,-0E
5rowser 6e# ser*er 4ata#ase Ser*er
,ocal $ost $ttp:77local $ost 7*dir7page name+$tml
9dir < 9irtual directory
5" -mage ,in&: ( -t is a non standard o#'ect and it consists of a set of non standard
properties+
@ #ro&en lin& (*alid 7 not *alid"
@ -mage content (+#mp of image"
@ Source (original pat$ of image"
@ -mage type (image lin& or image #utton or static image or dynamic image
(das$" or pre*iously sa*ed site image (#anners"
@ !R, (expected pat$ of next page"
SyntaxX(
3#'Yc$ec&Ygui (Jimage 8le nameK Jc$ec&list 8le name+c&lK Jexpected *alues
8leK time to create"X
31
C" Cell: ( -t is a part of we# page and it consists of a set of text lin&s and image lin&s+ %o
co*er t$ese all lin&s in a single c$ec&point we can depend on Jcell propertiesK+
%o get cell properties 8rst we can select o#'ect and t$en select required cell in
corresponding cell in t$at c$ec&list+
@ Cell 5ac&ground color (@$exadecimal"
W@#ro&en lin&s (cell area consists of many lin&s" (lin& name !R, /es 7 0o ((( 5y
default 0o"
@ Cell content (image 8le pat$s static text in t$at cell area"
@ .ormat (2ierarc$y of internal lin&s in t$at cell"
@ -mages (-mage 8le name type widt$ and $eig$t"
W@,in&s (lin& name expected !R, of next page w$en you clic& t$at lin&"
Syntax:(
6inYc$ec&Ygui (Jcell logical nameK Jc$ec& list 8le name+c&lK Jexpected *alues
of 8leK time to create"X
d" %a#le: ( -t is a non standard o#'ect and it consists of a set of non standard properties+
5ut t$ey are not suita#le to conduct !R,Vs testing (columns format rows ta#le
content"
6e can use ta#le properties to estimate co*erage of cells in your we# pages+
e" .rame :( (.rame is treated as 6indow"
-t is a non standard o#'ect and it consists of a set of standard and on standard
properties+ 6e can use t$ose non standard properties to conduct !R,Vs testing+
W@ 5ro&en ,in&s (lin& name !R, /es 7 0o"
@ Count o#'ects (0um#er of standard = non standard o#'ects"
@ .ormat (2ierarc$y of internal lin&s"
@ .rame content (Static text in we# page"
@ -mages (-mage 8le name type widt$ and $eig$t"
W@ ,in&s (lin& name expected !R, of next pages"
Syntax:(
6inYc$ec&Ygui(Jframe logical nameK Jc$ec& list 8le name+c&lK Jexpected *alues
of 8leK time to create"X
0ote: ( -n general test engineers are conducting !R, testing at frame le*el+ -f a frame
consists of $uge amounts of lin&s test engineer concentrates at cell le*el+
DQ7CC7NG
Static %ext %esting: ( %o conduct calculations and ot$er text #ased test we can use Jget
textV option in create menu+ -t consists of #elow su# options:
a" .rom o#'ect or window
#" .rom Selection
c" 6e# %ext c$ec& point
32
a" .rom o#'ect or window: ( %o capture we# o#'ect *alue into our *aria#le we can use
t$is option+
Syntax:(
6e#Yo#'YgetYtext(Jwe# o#'ect nameK J@ row num#erK J@ column num#erK
J*aria#leK Jtext #eforeK Jtext afterK time to create"X
Redi?
Mail #ox
S70o Su# .rom 4ate SiLe
B B B B F U5 @ C
B B B B C U5 @ D
B B B B ( @ F
@N @C @D @F @G
Expected: ( Sum (all recei*e mails" `<FM5
Sum<NX
SetYwindow(Jredi?K Q"X
3#'YgetYinfo(Jmail#oxK JrowsK n"X
.or ( i<CX i`nX i=="
[
we#Yo#'YgetYtext (Jmail#oxK J@K:- J@GK s J J J&#K C"X
sum < sum=s
\
if (sum `<FWCNDG"
tlYstep(JstepK NKcalec is passK"X
else
tlYstep(JstepK CKcalec is failK"X
@@@Ex D:( -n mail #ox ta#le of a#o*e example programmer maintains some siLes in &#
some siLes in M5+ %$e total sum `<FNNM5+
#" .rom Selection: ( 6e can use t$is option to capture static text from we# page into
*aria#le+
0a*igation:(
Create Menu
Z
1et %ext
Z
.rom Selection
Z
4rag on we# page
Z
Rig$t clic& to lea*e
Z
Select text #efore and text after
Z
Clic& o&
Syntax:(
6e#YframeYgetYtext (Jframe logical nameK *aria#le Jtext #eforeK Jtext afterK
time to create"X
33
Ex X( S23PP-01
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( ((
( ( ( ( ( ( )merican f xxx as ( ( ( ( ( ((
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( ((
( ( ( ( ( ( )ustralian f xxx as ( ( ( ( ( ((
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( ( (
( ( ( ( ( ( -ndian Rs: xxx 7( as ( ( ( ( (
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( ( (
Expected: ( -ndian rupees < )merican f WGQ = )ustralian f=FQ
SetYwindow (Js$oppingK Q"X
6e#YframeYgetYtext (Js$oppingK x J)merican fK JasK C"X
6e#YframeYgetYtext (Js$oppingK y J)ustralian fK JasK C"X
6e#YframeYgetYtext (Js$oppingK L JRs : K J7(K C"X
-f (L<<(xWGQ = yWFQ""
%lYstep(JstepK N Jcalec is passK"X
Else
%lYstep(JstepK C Jcalec is failK"X
c" 6e# %ext c$ec& Point: ( 6$et$er your speci8ed text is exist in we# page or not+
6e can specify text wit$ t$e $elp of text #efore and text after+
+$tm %B%
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( (( Y Y Y Y Y Y Y Y Y Y
( ( ( ( ( ( )merican f xxx as ( ( ( ( ( (( Y Y Y Y Y Y Y Y Y Y
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( (( Y Y Y Y Y Y Y Y Y Y
( ( ( ( ( ( -ndian ( ( ( ( ( (( ((((((((((((((
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (e ( ( ( ( ( ( (

o#'YgetYtext (JeditK x"X
we#YframeYtextYexists (Jframe nameK x J)mericanK J-ndianK"X
0ote: ( %$is type of c$ec&point allows DQP c$aracters as Maximum+ (C *aria#le
allows only DQP c$aracters"
6E5 .!0C%-30S
C" we#Ylin&Yclic& ( " :( 6e can use t$is function to record a text lin& operation+
Syntax :( we#Ylin&Yclic& (Jlin& textK"X
D" we#YimageYclic& ( ":( 6e can use t$is function to record image lin& operation+
Syntax: ( we#YimageYclic& (Jimage 8le nameK x y"X
F" 6e#Y#rowseYin*o&e ( " X( 6e can use t$is function to open we# page t$roug$
6in Runner+
Syntax: ( we#Y#rowseYin*o&e (W-E 7 0E%SC)PEK !R, J"X
Eg :(
6e#Y#rowseYin*o&e (-E $ttp:77www+ya$oo+com"X
34
6in Runner supports -E 7 0E%SC)PE #rowsers only for 6e# %esting+
@@@@
0a*igation: ( open /a$oo $ome page automatically
Z
Sign up now
Z
Register new use wit$ *alid *alues
Z RE1-S%ER
Close register window
Z
,ogin wit$ new user -4
Z
Clic& -n#ox to open mail #ox
Z
,ogout
C$ec& points:(
C" )fter creation of new !ser -4 Result window speci8ed !ser -4 < %est
gi*en !ser -4 in registration form
Registration Result 6indow
!-4 WWWWWWW Y Y Y Y Y Y Y Y Y
Y Y Y Y Y Y Y Y Y xxxeya$oo
Y Y Y Y Y Y Y Y Y Y YY Y Y Y Y
< <
D" ,ogin !-4 < Mail#ox s$owing !-4
6in Runner T+N *erses 6in Runner P+N:(
C" Run time record c$ec& (data#ase c$ec&point"
D" )uto ,earning
F" Per %est Mode
G" 6e# %esting facility
Q" Selecti*e Recording ( Record on speci8c Pro'ect"
P" 1!- Spy (6$et$er o#'ect is recogniLing or not"
,eftCtrl=fF (( %o stop SP/
DP7CC7NG
%ES%-01 43C!ME0%S
(Quality Control" %esting Policy
Company ,e*el
%esting strategy
(Quality )nalyst"
%esting Met$odology
%M7PM7%est lead %est Plan
35
Sn+ %est Engg
%est Cases
%est Procedures
%est Scripts Pro'ect ,e*el
%est ,ead %est Engg %est ,og
4efect Report
%est ,ead %est summary Report
C" %esting Policy: ( -t is a company le*el document+ %$is document de*eloped #y Quality
control people ()lmost Management"+ %$is document de8nes testing o#'ecti*e of our
organiLation+
WWWWWWWWWWWWW
WWWWWW )ddress line of Company
WWW
%esting 4e8nition: 9eri8cation and 9alidation
%esting Processes: Proper test planning #efore starts testing
W%esting Standard: C defect per DQN ,3C 7 C defect per CN .)
%esting Measurements: Q)M %MM PCM
WWWWWWWWWWWW
(C+E+3"
,3C > ,ines of code
Q)M > Quality )ssessment Measurements
%MM > %est Management Measurements
PCM > Processes Capa#ility Measurements
.P > .unctional Point
Ex: 0um#er of Screens
0um#er of -nputs
0um#er of 3utputs
0um#er of Queries
0um#er of .orms
0um#er of Reports
0ote: ( 4i?erent companies consist of di?erent testing standards+
D" %esting Strategy: ( -t is a company le*el document and de*eloped #y JQuality
)nalystK+ %$is document de8nes testing approac$ to meet policies speci8ed testing
o#'ecti*es+
36
Components in %est Strategy:(
a" Scope and o#'ecti*e: ( 4escri#e testing standards wit$ respect to our organiLation
le*el+
#" 5usiness -ssues:(
CNNO (Pro'ect Cost"
PGO FPO
(4e*elopment and %esting Cost
Maintenance cost"
c" %esting )pproac$
%est 4e*elopment i7f gat$ering 4esign Coding System testing Maintenance
.actors Stages : )nalysis
Ease of !se B B
)ut$oriLation
)ccess Control
Ease of 3perate
CQxQ
%est Responsi#ility Matrix (or" %est Matrix: ( %$is matrix de8nes mapping #etween
testing issues and de*elopment stages+
d" %est En*ironment Speci8cations: ( ,ist of testing documents to prepare during
testing+
e" Roles and Responsi#ilities: ( 0ames of 'o#s and t$eir responsi#ilities during testing
processes+
f" Communication and Status Reporting: ( 0egotiation #etween e*ery two consecuti*e
roles in testing team+
g" )utomation %esting and %ools: ( 0eed of automation in your company le*el pro'ects
testing+
$" 4efect trac&ing system: ( Required 0egotiation #etween testing team and
de*elopment team+ 6$en testing team got miss matc$es+
i" Ris&s and Mitigation: ( Estimates teature failures and possi#le solutions to wor&s+
'" C$ange and Con8guration Management: ( 2ow to $andle c$anges coming from
customers site during testing+
&" %esting Measurements and Matrix:(
C" Quality )ssessment Measurement
37
D" %est Management Measurement
F" Process Capa#ility Measurement
l" %raining Plan: ( Sc$edule for testing team to pro*ide training on pro'ect requirement
to understanding+
%est .actors: ( ) %est factor indicates a testing issue in general to de*elop quality
software+ %$ere are CQ common test factors+
Quality Control > Quality
Quality )nalyst > %est .actors (Ease of !se"
%est ,eader > %esting tec$niques (!ser -nterface %esting"
%est Engineer > %est Cases (Msw Rules"
C" )ut$oriLation: ( 9alidation of users to connect to application
D" )ccess Control: ( Permission to use speci8c ser*ice #y aut$oriLed user+
F" Correctness: ( Meet customer requirements
G" )udit %rail: ( Maintain metadata (data a#out user operation"
Q" Continuity of processing: ( -nter process communication or -ntegration of program
P" Coupling: ( Co(existence wit$ ot$er existing software to s$are resources+
T" Ease of use: ( !ser .riendliness
M" .ile -ntegrity: ( Maintains internal 8les
Ex:( c(o#' ( 8les #ot$ or created w$ile running+
S" Relia#ility: ( Reco*er from a#normal situation+
CN" Performance: ( Speed of processing+
CC" Porta#le: ( Run on di?erent platforms+
CD" Ser*ice le*els: ( 3rder of functionality
Ex: ( ,ogin after mailing logout orders > Serial
CF" Met$odology: ( 6$et$er required standards are following are not #y testing team+
CG" Maintaina#le: ( 6$et$er our software is long time maintaina#le in customer site or
not+
%est .actors *erses 5lac& 5ox %esting %eam:(
C" )ut$oriLation:(
Security %esting
Z
.unctionality 7 Requirement %est
D" )ccess Control:(
Security %esting
Z
.unctionality 7 Requirement %est
F" )udit %rail:(
H .unctionality 7 Requirement %est
Z
Error $andling testing
G" Correctness:(
38
)ll 5lac& 5ox %esting %ec$niques
Q" Continuity of Processing:(
Execution %esting
Z 6$ite 5ox %esting %ec$nique
3peration %esting
P" Coupling:(
-nter System %esting
T" Ease of !se:(
!ser -nterface %esting
Z
Manual Support %esting
M" Ease of 3perate:(
-nstallation %esting
S" .ile -ntegrity:(
.unctionality 7 Requirements %esting
Z
Reco*ery %esting
CN" Relia#ility:(
Reco*ery %esting (3ne !ser ,e*el"
Z
Stress %esting (Pea& ,oad ,e*el"
CC" Performance:(
,oad %esting
Z
Stress %esting
Z
4ate 9olume %esting
Z
Storage %esting
CD" Porta#le:(
Compati#ility %esting
Z
Con8guration %esting
CF" Ser*ice ,e*els:(
.unctionality 7 Requirements %esting
Z
Stress %esting
39
CG" Met$odology:(
Compliance %esting
(6$et$er t$e testing is followed on wit$ respect to standards of testing is going or not"
CQ" Maintaina#le:(
Complaints %esting
--- %est Met$odology: ( ) re8nement form f test strategy is called %est Met$odology+ -t is
a pro'ect le*el document+ %o prepare t$is document Quality )nalyst follows #elow
procedure+
C" 1etting %est Strategy
D" -dentify Pro'ect type
Pro'ect %ype -7f 1at$ering
)nalysis
4esign Coding System
%esting
Maintenance
%radition /es /es /es /es /es
3..Y%2EYS2E
,.
(3ut
Sourcing"
0o 0o 0o /es 0o
0o 0o 0o 0o /es
4epends on pro'ect type an audit decrease num#er of columns in %RM (%est
Responsi#ility Management" for t$at pro'ect testing+
F" -dentify )pplication type and Requirements:(
4epends on t$e steady quality analyst degrees in %+R+M+ for t$is pro'ect testing+
G" -dentify %actic Ris&s: ( 4epends on t$e study quality )nalyst degrees num#er of
factors %+R+M+
Q" 4etermine t$is scope of application: ( %$e study adds num#er of factors %+R+M+ wit$
respecti*e to future en$ancements+
P" .inaliLe %+R+M for current Pro'ect %esting:(
T" Prepare System %est Plan
M" Prepare module test plans if required
DS7CC7NG
%esting Process:(
%est -nitiation %est Planning %est 4esign %est Execution
40
Regression 4efect Report
%est Closer %est Reporting
PE% Process :( (Process Experts %ools and %ec$nology"
(4e*eloped #y 2C, ( C$ennai accepted #y Q) forma > -ndiaY
i7f gat$ering
(5RS"
Z
)nalysis (s7wrs" 5) 7 ., 7 5C
2,4 : ,,4 Study S76RS Quality )nalyst
Z Z %est ,ead
Coding %est planning
Z Z
!nit and -ntegration %esting %est Cases Selection
Z
%est cases selection re*iew
-0-%-), 5!-,4
Z
,e*el > 3 (Sanity 7 Smo&e 7 %)%"
Z
%est )utomation
Z
5atc$es creation (%est Suite 7 %est Set"
Z
5ug 8xing Modi8ed Select a 5atc$ and starts execution new
: 5ug Resol*ing Regression (le*el D"
,e*el ((C"
4e*elopment 4efect if you get a mismatc$ t$en -ndependent
Report suspend t$at #atc$
Z
3t$erwise
Z
%est Closer
Z
.inal Regression testing 7 Release %esting 7 Pre > )cceptance %esting
Z
!ser )cceptance %esting
Z
Sign 3?
-9 %est Planning :( )fter completion of met$odology 8naliLation for current pro'ect
corresponding test plan aut$or (Pro'ect Manager 7 %est ,ead 7 %est Manager 7 senior %est
Engineer" concentrate on system test plan document preparation to de8ne J 6$at to
testAK 2ow to testK J6$en to testK and J6$o to testK+ > %o prepare t$is type of test
plan document test plan aut$or follows #elow 6or&#enc$+
41
FN7CC7NG
4e*elopment Plan %eam .ormation
5RS S76RS -dentify tactical ris&s
6rite %est Plan System %est Plan
Re*iew test plan
Z
Z
%RM %est Engg
C" %eam .ormation: ( -n general t$e test planning process starts wit$ %esting %eam
.ormation+ -n t$is stage test plan aut$or depends on #elow factors:
@ )*aila#ility of %esters
@ %est 4uration
@ )*aila#ility of %est En*ironment Resources
WW %$ese F are dependent factors on eac$ ot$er WW
Case Study:(
%est duration:(
Client Ser*er 7 6e# 7 ERP > F to Q mont$s system testing
(ERP ( Enterprise Resource Plan"
System Software ( T to S mont$s system testing
(0etwor& : 2ardware"
Mac$ine critical ( CD to CQ mont$s system testing
%eam SiLe: ( F:C (de*elopment: %esting"
F > 4e*elopers C %ester
D" -dentify %actical Ris&s: ( )fter completion of possi#le team formation %est plan
aut$or concentrate on Ris&s analysis wit$ respect to pro*ided team and pro'ect
requirements+
Eg :(
@ ,ac& of &nowledge of test engineers on t$at domain
@ ,ac& of 5udget (time"
@ ,ac& of Resources
@ ,ac& of test data ()d > $oc %esting"
(Sometimes test engineer applies )d > $oc testing depends on Pre determined ideas"
@ 4elays in deli*ery
@ ,ac& of de*elopment processes Rigor (Seriousness 7 Sincerity"
@ ,ac& of communication in #etween testing team and de*elopment team+
F" Prepare %est Plan: ( )fter completion of team formation and ris&s analysis test plan
aut$or concentrate on plan document writing+
42
%esting document is going on -EEE format eit$er -S3 or Six Sigma or CMM Standards+
IEEE fo'mat 4In#tit+te of Elect'ical an( Elect'onic# En$inee'/
C" %est plan -4: ( !nique 0um#er 7 0ame
Eg : S%PY)%MY9C
(System %est planY)%MY9ersion C"
D" -ntroduction: ( )#out Pro'ect
F" %est -tems: ( Modules 7 Ser*ices 7 .eatures 7 .unctions
G" .eatures to #e tested: ( ) 5 C 4 () 5 > 9C 3ld" (C 4 ( 9D 0ew" Required features for
test design+
Q" .eatures to #e not tested: ( 6$ic$ ones and w$y notA
(3ld modules no need #ecause test data is already a*aila#le"
4epends on F G and Q > we can decide J6$at to %estK (on #ase of 5RS 7 S76RS"
P" )pproac$: ( ,ist of required testing tec$nique to test a#o*e features (6$at to test"
depends on ERM+
T" .eatures Pass 7 .ail criteria: ( 6$en a feature is passing w$en a feature is failing
(3ptional"+
M" Suspension Criteria :( (4onVt conduct testing on mailing w$en ser*er down"
Possi#le a#normal situations during a#o*e features testing+
S" %est En*ironment: ( Required 2ardware and Software to conduct t$ese features
testing including testing tools if possi#le+
CN" %est 4eli*era#les: ( Required %est documents to prepare during a#o*e features
testing+
(Case Procedure )utomation ,og Mismatc$ Reporting 0ames"
CC" %esting %as&s: ( 0ecessary tas&s to do #efore starts e*ery feature testing+
(P to CC 236 %3 %ES%"
CD" Sta? and %raining 0eeds: ( 0ames of selected test engineers for t$is pro'ect
CF" Responsi#ilities: ( 6or& allocation to selected engineers+
(CD to CF Y 623 %3 %ES%"
CG" Sc$edule: ( 4ates and %ime
(CG > 62E0 %3 %ES%"
CQ" Ris&s and Mitigation:(
CP" )ppro*ed 5y: ( Signatures of test plan aut$or and quality analyst (7 Pro'ect
Manager"
43
G" Re*iew %est Plan: ( )fter Completion of possi#le test plan document preparation test
plan aut$or concentrate on re*iew of t$at document for completeness and correctness
along wit$ test engineer to collect feed#ac&+
WW -n t$is re*iew t$ey concentrate on #elow co*erage analysis:(
@ 5usiness Requirement #ased > 6$at to test
@ Ris&s 5ased (6$o and 6$en to %est"
@ %RM 5ased (2ow to test"
Case Study:(
Sc$edule for Q mont$s of testing processes+
4eli*era#le Responsi#ility Completion %ime
%est Cases Selection E*ery mem#er in testing
team
DN > FN days
%est cases Re*iew %est ,ead : %est Engineer G > Q days
(R9M" Requirements
9alidation Matrix
%est ,ead C 4ay
%est )utomation (-ncluding
Sanity"
%est Engineers DN > FN days
%est Execution
(,e*el C > Real ,e*el (D
Regression "
%est ,ead and %est Engineer GN > PN days
4efect Reporting E*ery one in testing team 3n 1oing
Communication status
reporting
%est lead wit$ %est
Engineers
3n 1oing (6ee&ly %wice"
%est Close and Pre
)cceptance %esting
%est ,ead wit$ %est
Engineer
G > Q days
!ser )cceptance %esting Customer Side People G ( Q days
Sign of %est ,ead C > D days
C7CD7NG
9+ %est 4esign: ( )fter completion of test planning and corresponding wor& allocation
e*ery test engineer concentrate on selection of test cases for responsi#le modules+
4uring t$is le*el e*ery test engineer follows t$ree 5asic test case design
met$ods for Error($andling and Manual Support (%$ese are mandatory for e*ery
pro'ect"+
C" 5usiness ,ogic 5ased %est case 4esign
D" -nput 4omain 5ased %est case 4esign
F" !ser -nterface 5ased %est case 4esign
C" 5usiness ,ogic 5ased %est case 4esign: ( -n general test engineer are writing
maximum num#er of test cases depends on !se cases or .unctional Speci8cations in
S76RS+
44
) !se case descri#es t$at $ow a user can use a functionality in our system+
Eg :( ,ogin
5usiness Requirement
Z
!se Case %est Case
Z
2ig$ ,e*el 4esign 4ocument
Z
,ow ,e*el 4esign 4ocument
Z
Coding+exe
.rom t$e a#o*e model test engineer prepares a list of test cases depends on
corresponding use cases+ %o prepare t$ese test cases t$ey can follow #elow study:
Step C: Collect !se cases for responsi#le modules
Step D: Select a !se case and t$eir dependencies
Eg :( Mail ((((( ,ogin
!C
!C !C
4eterminants 4ependent
Step D+C: -dentify entry condition > 5ase state (6$ere - want to start module wor&"
Step D+D: -dentify input required > %est 4ata (4uring functionality testing w$at inputs -
$a*e to use"
Step D+F: -dentify output and outcome > Expected
Multiply ,ogin
i7p C D !id xxxx
i7p D F Pwd xxxx
3U 3U -053B
Result P
3utcome
3utput
Step D+G: -dentify exit condition (w$ere you stop t$at module testing" > End State
Step D+Q: Study normal dow > call states
Step D+P: -dentify alterati*e dows and exceptions
Step F: 6rite list of test cases depends on a#o*e study
Step G: Re*iew t$at test cases for completeness and correctness+
!se case C: ) login process allows !ser -d and Password to aut$enticate (*alid" !ser+
.rom data model !ser -d allows G to CP c$aracters long wit$ alp$a numeric in lower
cases+
45
Password allows G to M c$aracters long wit$ alp$a#ets in lower case+
%est case C: Successful entry of !SER -4
59) (SiLe" ECP (%/PE"
Min > G Pass 9alid -n*alid
Min (C ( F .ail a(L )(R
Min=C > Q Pass N(S Special C$aracter
Max > CP > passes 5lan&
Max > C (CQ > pass
Max = C > .ail
T7CD7NG
4efect )ge: %$e time gap #etween J4efect Reported onK and Jdefect resol*ed onK+
4efect Su#mission:(
CMM : -S3 > ,e*el > ,arge Scale 3rganiLations
Quality )nalyst
%est Manager Pro'ect Manager
2ig$ Se*erity Z Z
4efect Re'ected %est ,ead %eam ,ead
5y 4e*elopment Z Z
%est Engg 4e*eloper
%ransmittal Reports
Medium and Small scale Companies
Pro'ect Manager
%est ,ead %eam ,ead
Z Z
H %est Engg 4e*eloper
Z Z
%ransmittal Reports
Resolution %ypes:(
%esting 4e*elopment
4efect Report
46
Resolution %ype
)fter reporting a defect to de*elopment testing ream recei*e JResolution typeK from
de*elopment to concentrate on furt$er negotiation+
C" En$ancement: -t is not a defect may #e future requirement of customer
D" 4uplicate: 0ot a defect equal to pre*iously reported defect
F" 2ardware ,imitation: 0ot a defect raised due to $ardware limitation
G" Software ,imitation: 0ot a defect raised due to software limitation
Q" 0ot applica#le: Re'ected #y de*elopers may #e wrong idea of tester
P" .unctions as designed: 0ot a defect coding is correct wit$ respect to design
documents+
T" !sers misunderstanding: Extra 0egotiation
C( T ((( Re'ections
M" .ixed: 3pen #ug #y de*elopers
S" .ixed indirectly: )ccepted #ut not interested to resol*e
M(S ((((( )cceptance
CN" 0eed more information:
CC" 0ot Reproduci#le: /our speci8ed defect doesnVt appears in de*elopment site
CD" 0o plan to 8xit:(
CN > CD ((((( Extra 0egotiation
4efect Status:(
0ew
Z
4efect .ixing (((((((((( 3pen 7 Re'ect 7 4i?ered
Z
Close
Z
Reopen
5ug ,ife Cycle:(
4etect 4efect
Z
Reproduce 4efect
Z
Reporting 4efect
47
Z
4efect 8xing
Z
5ug Resol*ing
Z
5ug Closing
%ypes of 5ugs:(
C" !ser -nterface :( (,ow Se*erity"
D" 5oundary Related :( (Medium Se*erity"
F" Error > 2andling :( (Medium Se*erity"
G" Calculations :( (2ig$ Se*erity"
Eg:( -ntermediate wrong result (2ig$ Priority"
.inal 6rong result (,ow Priority"
Q" -mproper Ser*ice ,e*el: (Medium Se*erity"
P" Race Conditions :( (2ig$ Se*erity"
Eg: ( 4ead ,oc& 2ang 4ata#ase 4isconnect Compati#ility pro#lems -ntersystem"
T" ,oad Conditions :( (2ig$ Se*erity"
Eg: Memory ,ea&age Queue 3*erdow Sessions composition etcE"
M" 2ardware 4efects :( (2ig$ Se*erity"
Eg: Con8guration testing pro#lems 0et Connection .loppy 4ri*e"
S" 9ersion Control 4efects :( (2ig$ Se*erity"
Eg:( di?erences #etween two consecuti*e 5uilds
CN" -4 control 4efects :( (Medium Se*erity"
Eg: ( ,ogo Copyrig$t window
CC" Source 5ugs :( (Medium Se*erity"
Eg: ( Mista&es in 2elp 4ocument
9--- %est closer: ( )fter completion of all possi#le test cases execution and
corresponding defect trac&ing test lead concentrate on test execution closer re*iew to
estimate test completeness+
(((((( Co*erage )nalysis
@ 5R 5ased
@ !C 5ased
@ 4ata model 5ased
@ !- con*entions 5ased
@ %RM 5ased
((((((( 5ug 4ensity 7 5ug -n'ection Rate
(-n one module a*erage $ow many defects found #y testing team"
Eg: ( ) > DNO
5 ( DNO
C ( GNO (((((0eed of Regression
4 ( DNO
((((((
CNNO
(((((( )nalysis of deferred 5ugs: ( 6$et$er deferred #ugs are postpona#le to notA
)fter completion of test closer re*iew selected test engineers concentrate on 8nal
regression testing or pre acceptance testing+
1at$er Regression
48
Requirements
Reporting E?ort Estimation
Regression test Plan Regression
4epends on time only $ig$ density or entire pro'ect+
-x+ !ser )cceptance %est: ( )fter completion of Pre acceptance test and t$eir le*el
modi8cations testing team in*iteeVs customer side people to collect feed #ac& from
t$em t$roug$ management in*ol*ement+
%$ere are two possi#le approac$es in acceptance suc$ as:
C" )lp$a %estD" 5eta %est
B+ Sign 3?: ( )fter completion of user acceptance test and t$eir modi8cations test lead
prepares test summary report (%SR"+ -t is a part of S76R0( (Software Release 0ote"
%$is Summary report consists of
@ %est Strategy 7 Met$odology (%RM"
@ System %est Plan
@ Requirements 9alidation 7 %racea#ility Matrix (R9M 7 R%M"
(Mapping #etween customer requirements and test case designed #y tester"
@ )utomation %est Scripts
@ .inal 5ug Summary Reports
%$ese documents are called external documents #ecause we are gi*ing to
customer side+
.inal 5ug Summary Report .ormat
5ug -4 4escriptio
n
.ound 5y .eature Se*erity Status
(Closed or
4i?ered"
Comments
A,DITING
4uring testing and maintenance testing team conducts audit meetings to
estimate status and required impro*ements+
-n t$ese auditing processes t$ey can use F types of measurements and matrix+
C" Quality )ssessment Measurements (Q)M":( %$ese measurements used #y Quality
)nalyst or Pro'ect Manager to estimate )c$ie*ement of Quality in current pro'ect
testing
Mont2l Once
@ Product Sta#ility
49
0o+ 3f 5ugs 4efect )rri*al Rate duration
DNO %esting > MNO 5ugs
MNO %esting > DNO 5ugs
@ Su;ciency
Requirement Co*erage
Z
%ype > %rigger )nalysis
(Mapping #etween test and requirements co*ered"
@ 4efect Se*erity 4istri#ution
3rganiLation trend limit c$ec&
D" %est Management Measurements (%RM":( %$ese measurements are used #y test lead
during testing of current pro'ect+
Wee3l T*ice
@ %est Status
Executed %est cases
Z
-n Progress
Z
/et %o execute
@ 4elays in deli*ery (test ,eadN
4efect arri*al rate
Z
4efect Resolution Rate
Z
4efect ageing
@ %est E?ort
Cost (time" of 8nding a defect (G defect 7 Person > day"
F" Processes Capa#ility Measurements (PCM":( %$ese measurements are used #y
Quality )nalyst and test management to impro*e capa#ility of testing processes for
upcoming pro'ects testing (4epends o old pro'ects maintenance le*el feed #ac&"
@ %est E;ciency
%ype > %rigger )nalysis
Z
Requirements Co*erage
@ 4efect Escapes
50
%ype P$ase )nalysis
(6$at type of defect my testing team missed in w$ic$ p$ase testingA"
@ %est E?ort
Cost (%ime" of 8nding a defect+
51