aTesting ToolsManual TestingDefinition of Testing: -
Testingisaprocesswheretester intentionistodectednumber of defect
availableinSoftware. We need to test the software because it may
have failures at any one of the functionality. Test a software with
valid & invalid inputs (positive & negative testing) We
need to test the software to verify uncovered functionalities
available in software.Application: - Developing one software with
one specific customer
requirementsProduct:-Whereasproductmeansdevelopingdependinguponcurrentmarertrendfornumberofusers.Build:
- !inally integrated all modules which are ept in ".e#e$
(e#ecution) form are called a %uild.Types of Tools: -There are
following types of tools available show below1. Functional Tools: -
2. Performance Tools: - Win&unner 'oad &unner (T) *+meter
Sil Test web Tools &ational &obot *+unit Test ware
,ompo+ware3. Defect Tracing Tools: - 4. Configuration anagement
Tool: - (, ((uality ,enter) -SS ( -isual Source Safe) ,lear (uest
,-S ( ,ongruent -ersion System) %ug+.illa (, /0 ((uality ,enter /0)
,lips !oft"are #uality Assurance $!#A%: - 1t is a process which is
followed by the 2anagement in order tosetup agreement between
company management & client. 1t defines to monitors and measure
the totalstrengthdevolvementteamprocessaswell
astestingprocessinordertomaintaingoodrelationshipbetween client
& company management.#uality of Testing: - 1. 3 Tester should
have good communication sills as well as writing sills.2. 3 Tester
should have complete domain nowledge.3. 3 Tester should have
understood the current pro4ect business requirements.4. 3 Tester
should have able to identify the defects in the early stages5 in
order to avoid cost ofthe defects.5. 3 Tester should have
communicated with the development team6 in order to resolve
theissues when ever to required more information.!oft"are Testing:
- Software Testing is conduct testing on one application for
verification & validation.&erification: 1t done by
developers5 verified the internal process of the
applications.&alidation: - 1t done by (3 Team5 where testers
will validate the e#ternal structure of the application5 byputting
some data and checing output as per the customer requirements. 1
Testing Tools!oft"are De'elopment (ife Cycle $!D(C%:- 1t is a
mapping between various development stages & testing stages. 1t
defines proper planning for entirepro4ect development and also its
gives stage by stage to development software. 1t is first process
in everyorgani.ation before going for developing software.!tructure
of t)e #TP $#uic* Test Professional%:There are four parts can be
classified.1. Test Pane:- it will record what ever user can
performDialog$+(ogin,%.-in.dit$+Agent/ame,%.!et +mind0,7ere red
color indicated "8b4ects$ (Dialog).%lue color indicated "2ethods$
(Win9dit5 Set)2other window or )arent window ('ogin),hild window or
sub window (3gent:mae)-alues (mindq).2. Acti'e !creen: - which will
tae a snapshot on all ob4ects5 images and store some place.3. Data
Ta1le: -1t is a 2S+9#celSheet if default integrated when 1 want to
pass differentvalues into the (T) ((uic Test )rofessional) by using
Data Table.Design data table Data Ta1le: &un time table ;
8riginal table Design data ta1le: - 1t is a editable the values.
2un time data ta1le: - 1t doesn@1 (>raphical @ser 1nterface)
ob4ects5 propertiesvalues behavior lie Te#tbo#5 'istbo#5 )ush
button5 etc.$ii% 5nput Domain Co'erage: - ,hecing minimum si.e
& ma#imum si.e of the inputs.$iii% Calculation Co'erage: -
-erifying the 8utput ,orrectness.$i'% Bac*end Co'erage: -
-alidation database in two types Data -alidation (1nserting5
2odifying5 @pdating). Data 1ntegrity. Data &alidation: - what
operation user performs in the front end side whether it
iscorrectly specify in the bacend of our application.
Data5ntegrity: -what values wespecifyinthefront endsidewhether
therecorrectly specified in the bacend columns at respective to
columns.$'% .rror 8andler Co'erage: - )reventing "@n e#pected
events occurring during at run time$.$'i% !er'ice (e'el Co'erage: -
,hanging order of functionalities of our application.$1% 5nput
Domain Testing: - 1t is a part in !unctional testing5 during this
process tester are validatingthecompletesi.e5
typeandrangeevery1nput ob4ects. Sotesterwill
followthebelowmathematicalnotations. %oundary -alue 3nalysis.
9qualance ,lass )artition. Boundary &alue Analysis $B&A%: -
To calculating the si.e5 range and types of ob4ects. 2inimum
)ass2a#imum )ass2inimum G / !ail 2a#imum G / )ass2inimum ?/
)ass2a#imum ? / !ail. .0ualance Class Partition: - 1n this case
checing ob4ect of values are valid or invalid. 13 Testing
Tools.:ample $6%: -1nsurance application follows number of policies
when user selects Type K3< policy fromtype drop down5 then
system as age of the person. They age should be gather than /L
years and shouldless than F0 years. )repare %oundary -alue 3nalysis
(%-3) and 9qualance ,lass )artition (9,))H!olution: - 7ere we come
under the range5 because it is To and !rom range1. Boundary Value
Analysis: - Condition: - /. age M/L yearsB. ageE F0 years
Conditions&alues 2esults2inimum ( M/L) /I Nears )ass2a#imum(
EF0) IO Nears )ass 2inimum G / (/I+/) /L Nears !ail2a#imum +/
(IO+/) IF Nears )ass2inimum ?/(/I?/) /F Nears )ass2a#imum?/(IO?/)
F0 Nears !ail2. Equalance Class Partition: - Condition: - /.
&anges only.&alid 2ange 5n'alid 2ange0+O 3 G P
a G . %lan space Special characters.:ample $2%: -3 login
application process allows user to authori.ed5 username ob4ect
allows A to B0characters along with alphabets & numeric in
lowercase5 where as password ob4ect allows only alphabetsfrom A to
/0characters alongwith uppercase. )repare %oundary-alue
3nalysis(%-3) and 9qualance,lass )artitions (9,))H!olution: - 1n
this application have two ob4ected that are username &
password. We have prepared twoob4ects one after one. 1. Boundary
Value Analysis for Username (Sie!:-,onditions= + /. A to B0
characters of alphabets and numericB. 'owercase.
Conditions&alues 2esults2inimum ( A ) A )ass2a#imum( B0) B0
)ass2inimum G / (A+/) C !ail2a#imum +/ (B0+/) /O )ass2inimum
?/(A?/) Q )ass2a#imum?/(B0?/) B/ !ail 14 Testing Tools(ogin Page2.
Equalance Class Partition for Username: - Condition: - /.
&anges only.&alid 2ange 5n'alid 2ange0+O 3 G Pa+ .%lan
space Special characters1. Boundary Value Analysis for Pass"ord
(#e$t!:-,onditions= +/. A to /0 characters of alphabets.B.
@ppercase. Conditions&alues 2esults2inimum ( A ) A )ass2a#imum(
/0) /0 )ass2inimum G / (A+/) C !ail2a#imum +/ (/0+/) O )ass2inimum
?/(A?/) Q )ass2a#imum?/(/0?/) // !ail2. Equalance Class Partition
for Username: - Condition: - /. @ppercase&alid 2ange 5n'alid
2angea + . 3 G P %lan space Special characters0 G O$c% 5nter !ystem
Testing $)enetration ; ,oupling ; 9nd+to+9nd%: - 1t is also called
)enetration or ,oupling or 9nd+to+9nd Testing. During this process
a tester have tovalidates whether our current version()ro4ect) is
able to co+e#isted with other software application whichare
e#isting with the customer in order to share common resources. This
testing can be followed where wehave specific customer
requirements..:ample: -
15 Testing Tools 1nthis abovee#amplewehaveshows that 1nter
System. 7eretheredoalreadye#istingthefewapplications lie"9lectrical
%ill (9%)5 Telecom%ills (T%) andWater %ills
(W%)$5nowweaddingnewcomponent or application lie "1ncome Ta# (1T%)
in the co+e#isted the database. 7ere tester will to checall the
applications are run properly or not. 1t can chec sharing the
common resources lie printers5 etc.will all servers and
applications.$d% 2eco'ery Testing $&eliability Testing%: - 1t
is a :on+!unctional Testing5 because it is not a customer
requirement it is a system requirementtesting. 7ere finding
accuracy of testing using recovery testing.
1tisalsonownas&eliabilitytestingduringthisprocessatesterhastovalidatewhetherourapplicationisabletorecover
fromabnormal conditionstonormal
conditionsbyusingsomebacuptechniques. 1n this process the tester
may use bacups & procedures lie restarting a ,)@ or
checinginternal bacups created by developers.T)e reasons to go to
a1normal conditions are 7ardware & Software not supporting.
Database connectivity failures. Server connectivity failures.
8verload.$e% Configuration Testing: - During this process a tester
have validate whether our application %uild supports to
differenttype of hardware devices lie different types of printer5
:1, (:etwor 1nterface ,ard)5 topologic5 etc. it isalso called as a
sensitively testing.$f% Compati1ility Testing: - 16 Testing
ToolsDuringthisprocessatesterhavetovalidatehowwell
ourapplication%uildisabletorunondifferent typesof
8S(8peratingSystem)andalsoatester havetovalidatetothedifferent
typesofbrowsers in order to chec the compatibility of an
application.1n real time testers will face problems in bacward
compatibility verification and also a tester canrun the test cases
on different types of 8S(operating System) lie WindowsI5 Jp5
etc.5$g% 5nstallation Testing: - Thisprocess oftestingcan be
followedsoonaftergettinginitial%uildfromadeveloper.%eforegoingforinstallinganysoftwareatesterhavetomaesuresupportedsoftwareareproperlyconfiguredoncustomer
e#pectedconfigurationsystem. Whileinstallingsoftwareatester
havetogothrough initiali.ation guide which is provided by
developer. $)% Parallel Testing: -3fter completion of entire
functional testing5 before going to release any product
tocustomer5atesterhavetocomparenewversion%uildinordertofindoutdifferenceinrequirementenhancements
etc. and also management will compare our current pro4ect product
with other companyproducts in order to find out computation in the
maret.$i% 7ar1age 9 !anitation Testing: - duringthisprocessatester
havegothroughS&S(Software&equirement Specification)document
to finding out any e#tra features are added for the current
pro4ect. 1f any thing added a testerhave to verify that
functionality.$555% Performances Testing: - (it is a only seeing
9#pectation -alues or results only)This process can be followed
whenever we want to go for estimating speed of processing ofour
application %uild5 depending upon customer e#pected configuration
system and customer e#pectedload. 1t again divide into the below
following techniques. 'oad Testing. Stretch Testing. Storage
Testing. Data -olume Testing. (oad Testing: -
1tisalsonownas"Scalability$Testing(2easuring).Thee#ecutionof
ourapplication%uilddependinguponcustomer
e#pectedconfigurationsystemsandcustomer e#pectedloadinorder
toestimate the speed of processing of application build. 3 tester
also has to verify. 17 Testing Tools !tretc) Testing: - The
e#ecutionof our applicationbuilddependinguponcustomer
e#pectedconfigurationandcustomer e#pected un+intervals of load to
estimate pee load capacity of our application. 1f testers
aregettinganyvariationswiththepeeloadthentester
havetoinformtothedeveloper totunetheapplication. !torage Testing$
,apacity%: - During this process a tester have to validate the
ma#imum storage capacity of our applicationdependinguponcustomer
e#pectedconfigurationcomputer. 1nthis process atester
shouldhaveminimum :etwor nowledge to analysis storage capacity.
Data &olume Testing$Si.e%: -During this process a tester has to
validate the ma#imum si.e of the application dependingupon customer
e#pected load and configurations.$i'%!ecurity Testing: -it is a
comple# testing in %lac %o# Testing(%%T). During this process
tester have to validateprivacy of applications which are developed
by development team. This testing can be followed by somee#perience
persons in encryption and decryption will be performed by
development team where as testerswill follow the below two
technique. 3uthori.ation Testing. 3ccess ,ontrol Testing.
Aut)ori@ation Testing: -During this process tester have to validate
whether ourapplication %uilds allows valid users and prevents
invalid users..:ample: - 3ll %aning sectors5 login operations5
credit cards5 3T2 applications etc.
Access Control Testing: - During this process a tester have to
validate whether valid useris able to use some specific services
and also a tester have to validate the access control of
theapplicationDifference 1et"een t)e Functional < /on-Functional
TestingFunctional Testing /on-Functional Testing-alidating one
customer business requirement. Dealing with System related.3 tester
has to give more importance for!unctional requirements while
designing testingand e#ecuting test case.We give mediumpriorities
while design andrunning test case. !unctionality Testing. 1nput
domain Testing. &ecovery Testing. 1nstallation Testing. 18
Testing Tools 1nter System Testing. Security Testing. ,onfiguration
Testing. ,apability Testing. )arallel Testing. >arbage Testing.
)erformance Testing.;ser Accepting Testing $;AT%: -3fter completion
of entire functional testing on one application our product
management team willconcentratetocollectedfeedbacfromthereal
customersandreal liecustomer.1nthisprocesswefollowed two type of
testing that are 3lpha () Testing and %eta () Testing.Alp)a $%
Testing Beta $% Testing1t is done for software applications. 1t is
done for software products.3lpha Testing is done by 9nd+@sers
infront of the entire development teamprocess.1t is done by Testing
Team in front of thereal lie customer lie %&S5 developerteam.1t
is a real+environment. 1t is virtual+environment. 1n generalevery
client will release %eta () versionto the customersin order
tocollect feedbac5 in real time scenarios a tester have to conduct
live testing on %eta () version in front ofthe customer.aintenance
Document: -3fter completion of successful @ser 3ccepting Test(@3T)
process a tester have to a maintain all type ofdocuments for future
references5 if any customer suddenly request. Testing During
aintenance: -3fter completion of successful @ser 3ccepting
Test(@3T)5 management team willconcentrated to release the product
; application to the customer. 1n this process management team
willselect few developers and few testers and one hardware engineer
to go to onsite in order to train thecustomer which is called as
")ort$ testing.Port Testing: - 3fter reaching to the customer the
release team have to train the customer in the belowprocess.
,ompact 1nstallation. 1nput Devices handling. 8utput Devices
handing. )rimary (,urrent )ro4ect) and Secondary (7ardware &
Software Devices) handing. ,o+e#isting with other software
applications.3fter completion of training session release team will
be bac to company and follows as usual.!oft"are C)anges: - 19
Testing ToolsThis comes under maintenance or supportingthe customer
for anyenhancements orchanges requested required for developing new
version.Testing Te)minologies $o)( *ethodologies $6%. on*ey
Testing: - 3 tester conduct a testing only one basic functionality
modules or tester cases which are frequently usedby the customer.
This terminology can be follow when ever we donmail. 1f anyinvalid
data enter alter messages should be display and should tae bac to
the 'ogin screen. 32 Testing Tools!olution: -1n this application
have two ob4ects that are @sername & )assword. We have prepared
twoob4ects one after one. 1. Boundary Value Analysis for Username
(Sie!:-,onditions= +/. A to B0 characters of alphabets and
numeric.B. 'owercase. Conditions&alues 2esults2inimum ( A ) A
)ass2a#imum( B0) B0 )ass2inimum G / (A+/) C !ail2a#imum +/ (B0+/)
/O )ass2inimum ?/(A?/) Q )ass2a#imum?/(B0?/) B/ !ail2. Equalance
Class Partition for Username: - Condition: - /. &anges
only.&alid 2ange 5n'alid 2ange0+O 3 G Pa+ .%lan space Special
characters1. Boundary Value Analysis for Pass"ord
(#e$t!:-,onditions= +/. A to /0 characters of alphabets.2.
Equalance Class Partition for Username: - B. 'owercase.Condition: -
/. 'owercaseConditions&alues 2esults2inimum ( A ) A
)ass2a#imum( /0) /0 )ass2inimum G / (A+/) C !ail2a#imum +/ (/0+/) O
)ass2inimum ?/(A?/) Q )ass2a#imum?/(/0?/) // !ail&alid 2ange
5n'alid 2angea + . 3 G P %lan space Special characters0 + OTest
Case Procedure for ;se Case $6%: &erify t)e (oin
Functionality.Test Case5dTest Case/ame!tep/ameDescription .:pected
2esults T,S@,S00/-erify the'ogin!unctionalityStep /
Pur&ose:-The purpose of this Testcaseistoverifywhether @ser
isable to 'ogin in to >mailapplication with -alid permissions 33
Testing ToolsActors:- @serPre-Conditions:-1t should beauthori.ed in
to >mail.Step B 8pen 19 (1nternet 9#plore) %rowser and enter
@&'= www.gmail.com clic on >o button.@ser ; System is
display with"Welcome to >mail$ pagewith the following
fields.@sername= Te#t)assword = Te#tStep C 9nter
@sernameand)asswordinTe#t field with -alid te#t and clicon "Sign
in$ button.@ser;Systembedisplayedwith main page of >mail.Step A
9nter @sernameand)asswordinTe#t field with 1nvalid te#t and clicon
"Sign in$ button.@ser ; Systemis displayedwith alert message 9rror
2essage= "1nvalid @sername & )assword$
;se Case $2%: - &erify (ogon !ystem;se Case 5d :
S2!S@,S00/;se Case /ame = 'ogon System Actors : @serDescription: -
9very @ser needs to 'ogon the System in order to @se its
functionality. This @se,ase captures the requirements related to
'ogon System. Pre-Conditions = + :one;ser Action !ystem 2esponse(/)
@se ,ase starts when userrequestssystemthat7e;Shewantsto use the
,912S functionality.(/). System -alidate the user provided
details(B). System matches the user ;se Case
DesignDocumentDe'eloped Test Cases
'oginStepsRRRRRRRRRRRRRRRRRRRRRRRRRRR Deleting RRRRRRRRR:ew Student
)rofile StepsRRRRRRRRRRRRRRRRRRRRRRRRRRR 3ddingRRRRRRRRR1n the
above review documents developed by (3 'eas or (3 2anager in order
to maintain completeness &correctness of all test cases. 3nd
they will decide what the test cases to be done under 2anual are
& whatarethe testcasesto be done under3utomation.This isthe
finali.eddocumentforentireapplicationtesting.Build &ersion
Control: - 8ld -ersion2odify %uild:ew -ersion !T) ; 1),reate :ew
!older. :ew -ersion Fig: - Build &ersion Control 3fter
completion of entire development team process deployment team will
concentrate to deploythe current version build into soft base in
server with respected to supported software) (>raphical )oints)5
faults or database or filecorruptionorpotentialdata loss5 program
hangsrequiringrebootarealle#amples of a Severity / bug.B 2a4or
2a4or system component unusable due to failure or incorrect
functionalitySeverity B bugs5 cause serious problems such as a lac
of functionality orinsufficient or unclear errors messages that can
have a ma4or impact to theuser5 prevents other areas of the
application from being tested etc. SeverityB bugs can have a wor
around5 but the wor around is inconvenient ordifficult. C 2inor
1ncorrect functionality of component or process. These are a simple
woraround for the bug if it is Severity C.A Trivial Documentation
errors or signed off severity C bugs.F. Detected in -ersion= + The
name of the -ersion in which the above defect is found.O.
&eproduciable (Nes;:o)=+ 1f Nes= + The defect is "always
appearing$ the tester can select Nes.1f :o= +The defect is "rarely
appearing$ the tester has to select :o and should give strong
reason fordeveloper to understand by given the snapshots./0.
Status= + 3 tester has to select status of the defect dependingupon
the type of the defect. :ew= Defect found first time in application
8pen= 9ntering the defect for first time. &esolved=Developer
will changes toresolvedstatus when ever it is fi#ed. ,lose=3fter
retestingthedefect atester willclose by given some (3:otes5 if it
is woring as pere#pected. Duplicate=1f the defect already e#ists
adeveloper can changed to duplicate. Deferred=)ostponing a defect
if it is related to enchantment or if the defect is lowpriority or
low severity. Submitted= When we entered a defect into a defect
tracing tool. 1f it is a defaultstatus5 called as submitted.
1n+)rogress= When ever a developer is woring on any issues the
status of the defectis will be in progress. 3ssigned= when ever
defect is assigned to one concerned developer then status willbe
assigned. 9nchantment= when the tester entered defect is not
related to current version testingthen they will change to
enchantment.//.!unctional 3rea= + 3 tester has to select concerned
module for the above defect or selecting a moduleto which it is
belonging. /B. Sub+!unctional
3rea=+3testerhastoselectthesubfunctionalitytowhichtheabovedefectisbelonging.
44 Testing Tools/C. Defect Type=+ 3 tester has to select the type
of the defect that is entered. Default defect type is K,ode Defect
< Bug:-.rror: -The mistae had done by human being while coding
software during @nit Testing is called an9rror. 3n 9rror can lead
to failure which cans leads to fault.Defect: - The mismatch which
occurred during our test e#ecution when comparing e#pected results
withapplication behavior values.(or) The functionality which is not
behaving as per customer e#pected business requirements. 3defect
can also found the customer during production. Bug: - The defect
which is accepted by the developer to resolve it is called as
%ug.Defect Age: - The time gap between defected on and re+solved on
is called defect age.Defect (ife Cycle: - 1. Small Scale
Organization: -
7igh )riority ?7igh Severity:egotiation between Tester &
Developer. 45 Testing Tools2. Large Scale Organization: -V7igh
)riority ? 7igh Severity
,ommunication betweenTester & Developer/ote: - 3s per the
above process tester are not suppose to report the defects directly
to the developmentteam. The defects should be reviewed (3 'ead5 (3
2anager and should get approval.Defect !tatus 9 Bug (ife Cycle: -
3ccept &e4ect 1f it is !ailed&etestBy #A Team De'eloper
)ass
46 Testing Tools2esolution Types: - When a tester are reports to
the developer he will e#ecuted the same test case inthis system and
pass some resolutions type to (3 Team.1. Duplicate= + Developer
re4ect defect due to already e#isting of the defect.2. 9nchantment=
+ &e4ect defect due to not belong to current version5 we should
targeted forup coming version.3. :ot 3pplicable= + Developer is not
accept & re4ect but he required more information aboutissues.4.
!unction as Design= + Woring as our test case designee so developer
is re4ecting.5. :ot &eproducible=+ Developer is not accepting
& re4ects the defect5 but he required morestrong reasons to wor
on that issues.6. !i#= + 3ccepted for resolving.7. Software &
7ardware limitation= + Developer re4ect defect due to defect is
related to S;W &7;W.8. 2iss @nderstanding=+Developer is not
accepting&re4ect but requesting([email protected] (ife
Cycle: -(3 TeamDeveloper (3 Team 47 Testing ToolsTypes 3f Bugs: -/.
@ser 1nterface %ugs ('ow Severity). @nderstandable of Screens (7igh
Severity). Spell ,hecs (7igh Severity).B. 1nput Domain %ugs (7igh
Severity).C. ,alculation %ugs (7igh Severity).A. Security %ugs
(7igh Severity).Q. Database %ugs (7igh Severity).L. 'oad ,ondition
%ugs (7igh Severity).I. 7ardware & Software %ugs (2edium
Severity).F. &ace ,ondition %ugs (7igh Severity).O. %uild
-ersion ,ontrols (7igh Severity)./0. 1dentification ,ontrols ('ow
Severity).//. !unctional %ugs (7igh Severity).$G% Test Closer: -
3fter completion of the entire functional testing on the current
pro4ect5 (3 'ead will concentrateto develop finial review document
in order to submit to the 2anagement and develop the
documentationwhich is called as !inal Test Summary &eport
(!TS&). This is the part in Software &eleasing :otes
(SW&:)To develop Software &elease :otes (SW&:) to above
document are required to finali.e. The Software &elease :otes
(SW&:) document consist of1. )urpose.2. !eatures.3.
!unctionality that are completed.4. System &equirement.5. %ugs
,losed.6. Tnown 1ssues ; %ugs.7. &elease 2ode ; 2edium. 48
Testing Tools-)at is t)e Testing Process "e are follo"ing in our
organi@ationH $1nterview (uestion%(3 Team (3 'ead1999 (3 'ead ;
)2;)2 (3 ; )2 49 Testing Tools Sign8ffSing in @3T (@ser 3ccept
Test)!ign 5n: -1t is a process which is followed by the 2anagement
in order to setup agreement betweencompany management & client.
1t defines to monitors and measure the total strength devolvement
teamprocessaswell astestingprocessinorder
tomaintaingoodrelationshipbetweenclient
&companymanagement.5nformation7at)ering: -This is thefirst
stepandverycrucial steptocollectingall informationregarding to the
developed pro4ect or application. This is done by the %&S
peoples.1n 9very ,ompany followed the -+2odel to maintain the
better quality.&-odel: - 1t is a mapping between various
development stages and testing stages. - G Stands for"-erification
& -alidation$. 1t can be followed by large scale organi.ation
as it is e#pensive model. %utwhere as small scales will follows
!unctional & System Testing as mandatory. %ecause it is a
bottlenecphase.!tage $6%: Test 5nitiation:- 1t is the first process
that should be followed by very organi.ation in order to gather
client businessrequirement. That contains of %&S. This document
can also be called "@ser &equirement Specification$ (@&S)
or ",lient ;,ustomer &equirement Specification$ (,&S) or
"%usiness &equirement Document$ (%&D) or
"!unctional&equirement Specification$ (!&S).1t is a company
level document as well as pro4ect level document which should be
developingfor the entire development team & tester team. This
document defines approaches5 guidelines5 pro4ectplanning5 schedules
and tass that should be followed for the current pro4ect.5dentify
t)e Type of t)e Pro4ect: - 7ere the (3 2anager or )ro4ect 2anger
will involved identifying the type of the pro4ect and it
willconcentrate to the ne#t step. !oft"are 2e0uirement
!pecification $!2!% 9 ;se case Document $;CD%: -3fter completion
ofdevelopingof %&Sdocumentbusinessanalysispeoplewill
concentratetodevelopedaS&Sdocumentbasing on %&S document.
This document defines customer use cases5 requirements and
systemrequirements to be developed on new software. The contents of
S&S document are @se case Diagrams. 50 Testing Tools @se cases.
Tas flow Diagrams. )ictorial Diagrams (optionally). 3ctors.
)reconditions. )ost conditions5 etc.3fter completion of developing
S&S documents it will be send to customer ; client to get
approval./3T.: - 3 tester will develop test cases basing on this
S&S information. Design: - 3fter completion of information
gathering and developing a software design category people
willconcentrate to design architecture the application. 1n real
times to get approval from client side they willbe designing marup
design basing on S&S document.3fter getting approval from
client side they will enter in to detailed design to
developdatabase front+end from ob4ects lie te#tbo#5 list bo#5
checbo#5 radio button5 etc.5 To design a softwarethey follow the
below two process 7igh 'evel Design (7'D). 'ow 'evel Design (''D).
8ig) (e'el Design $8(D%:- 7igh 'evel Design document define the
overall hierarchy of all functionalities from leafmodule to root
module. (o" (e'el Design $((D%: - 'ow 'evel Design document defines
the "1nternal process of every sub modules$ thatare available in
one application. 1t is also called as an "1nternal 'ogics$.Coding:
-3ftercompletionof designsoftwareaprogrammer will
concentratetophysicallyconstructsoftware. This also called as
"1mplementation$. 3 programmer will follow different technical
techniques tocode software. The most commonly followed languages
for any software development ,5 ,??5 *ava5 Dot:et5 etc. after
completion of coding a software a programmer will follow some white
bo# testing (W%T)technique to verify logical errors5 synta# errors5
loop termination5 etc.-)ite Bo: Testing: - ;nit Testing: - (7ere
Tester not involved only developers) 1t is the first technique
which is followed by developer after coding software during this
process aprogrammer wills constructs to encounter errors5 fault5
and failures in a written coding.Blac* Bo: Testing: -3fter
completion of entire development team process a tester will receive
initial %uild from a developmentteam5 where tester can download by
using !T) (!ile Transport )rotocol) or 1) (1nternet )rotocol).!mo*e
Testing: - 51 Testing Tools%efore going for either 2anual or
3utomation testing a tester have to verify the initial buildwhether
it is a stable or un+stable. 1f it is stable tester will accept5 if
it is un+stable tester will re4ect andgive strong reason to the
development teams which is called as "Smoe Testing$.%lac %o#
Testing (%%T) is again divided in to the below A Techniques. 1.
@sesibility Testing.2. !unctional Testing.3. )erformance Testing.4.
Security Testing.5dentify t)e Current 2e0uirements: -To develop
pro4ect level document pro4ect manager will follow various types of
steps as shown below.!tep $6%: - )ro4ect 2anager to requite
resources for the current pro4ect testing.!tep $2%: - )ro4ect
2anager to go through (3 documentation to under stand the
approaches we follow.!tep $3%: - )ro4ect manager to identify the
type of the pro4ect that is received to our organi.ation.!tep $4%:
- )ro4ect 2anager have to determine current pro4ect requirements
which are necessary for our current pro4ect testing. !tep $A%: -
)ro4ect 2anager identify the feature requirements of the current
pro4ects testing5 so )ro4ect2anager will add some of the factors
which are required in feature for the current pro4ects. !tep $B%: -
)ro4ect manager has to identify the tactical riss that are involved
in the selected T&2 ,olumns5 so )ro4ect manager dependent upon
riss )ro4ect 2anager will delete some of the !actors from the
T&2 table and finali.e the factors for the entire pro4ect
testing. 3fter !inali.ing T&2 columns )ro4ect 2anager has to
develop )ro4ect planning forthe entire year by given schedules5
tass5 approaches for the entire pro4ect.5dentify t)e Tactical
2is*s: - 2is*s:&is is a problem that we are facing in
organi.ation lie lac of time5 lac of budget5 lac of &esources5
lac of preparation documentations5 delays and delivery of build5
etc.itigation: To over came the above problems (3 2anager will go
other alternate things methods to achieve ob4ectives.Approac) t)e
.ntire Team: - 7ere the (3 2anger ; (3 'ead will assign the
&oles & &esponsibility. &oles are "Designations$ of
theemployee and &esponsibility taes an each roles.!tage $2%:
Test Plan: - $%y (3 'ead%3fter a compilation of both company &
pro4ect level documents (3 'ead will concentrate todevelop test
plan document 1999 format. To develop test plan document (3 'ead
have to go throughvarious types of document in order to develop a
very good test plan.3fter completion testing team formation and
identifying riss (3 'ead will concentrates to develop a testplan
document for the entire formed (3 Team. This document defines
approach5 roles & responsibilities5time duration of the pro4ect
and environment to be used. 3nd also e#plain Who to testH What to
testH To develop the beside test plan some companies follows 1999
format. 52 Testing Tools When to testH 7ow to testHThey follow the
entire /L steps to prepare the test plan for the current
version.!tage $3%: Test Design $ )repare the Test cases %: -This is
the ma4or part involves of the tester for design test cases in the
real times. 3 testercan develop test case for any application lie
:ew &equest. 9nhancement. Defects. @ser 3ccepting Test
(@3T).%efore going for test cases a tester have under gone some
training in order to capture thementire customer business
requirements as per the test plan. The document tester follows to
design testingcases.1. S&S ; !S ; &equirement Document ;
@se case Document ; Technicaldocument ; DesignDocument2. Test plan
document and some time will follow test strategy documents.To
develop test cases5 the tester will follow below three
methods.et)ods: 1. %usiness &equirement %ased Test case
design.2. 1nput Domain %ased test case design.3. @ser 1nterface
(@1) %ased test case design.et)od 6: - %&S S&S@se ,ase Test
,ases.et)od 2:- %&S Design DocumentData 2odels (9& 2odels)
Test ,ases.et)od 3: - )erform cosmetics functions.!tage $3.6%: 2T
$or% &T:-3fter completion of developing Test cases for the
current version of all functionality (3 'ead or(3 2anager will
concentrated to review all the test cases for the completeness
& correctness5 and developa documentation called as
&equirement Traceable 2atri#es (&T2) or -alidation
Traceable 2atri#es (-T2).This document defines mapping between the
developer test case and the customer requirements. &eview
documents developed by (3 'eas or (3 2anager in order to
maintaincompleteness & correctness of all test cases. 3nd they
will decide what the test cases to be done under2anual are &
what are the test cases to be done under 3utomation. This is the
finali.ed document forentire application testing.!tage $4%: Test
.:ecution: - 3fter completion of entire development team process a
tester will receive initial build fromdevelopment team and once
they complete installing successfully they can test the
applications in twotypes there are/. 2anual Testing.B. 3utomation
Testing.3ftercompletionof
entiredevelopmentteamprocessdeploymentteamwill
concentratetodeploythecurrent version build into soft base in
server with respected to supported software