Manual Testing

Software Quality:
Software satisfies quality only when it meets to Customer Requirement / Customer Satisfaction /
Customer Expectations. Meets Customer Requirement refers to proper output & Customer Expectations refers
to extra characteristics, good interface, speed, priacy, security, easy to operate, good functionality.
!on"technical reasons# Cost of product & $ime to mar%et
Software Quality Assurance:
S&' are the Concepts to (e followed (y company to deelop the software. 'n S&' team is responsi(le
for Monitoring & Measuring the strength of deeloping processes.
Software Project:
' set of pro(lems assigned (y the client, who can (e soled (y the software people through the process
of software Engineer called Software pro)ect. *n short, the pro(lem, the people, the process called pro)ect.
Software related pro(lem is soled (y software engineers through software engineer process is software pro)ect.
Software Development Life Cycle / Life Cycle Development:
Stages inoled in software pro)ect deelopment
+, *nformation gathering- Customer requirement
., 'nalysis- Customer requirement /s Solutions
/, 0esign- 0iiding the pro)ect into modules & coupling them
1, Coding- 2hysical construction of pro)ect
3, $esting
4, Maintenance
nformation gat!ering stage:
*n this stage, 5usiness 'nalyst studies the requirement of the client /customer and they prepare 5usiness
Requirement Specification 65RS, documents.
Analysis:
*n this stage, Sr. 'nalyst prepares Software Requirement Specification 6S/w RS, document with respect
to corresponding 5RS document. $his document consists of two su("documents System Requirement
Specification 6SRS, & 7unctional Requirement Specification 67RS,. SRS contain details a(out software &
hardware requirement. 7RS contains details a(out the functionality to (e used in pro)ect.
Designing:
*n designing phase, 0esigners creates two documents 8igh 9eel 0ocument 6890, & 9ow 9eel
0ocument 6990,. 890 consists of main modules of the pro)ect from root to leaf and multiple 990:s. 990
consists of su("modules of main module along with 0ata flow diagrams, ER"0iagrams, etc., are prepared (y
technical support people or designers called *nternal designers.
5lac% (ox tester should hae %nowledge of customer requirement
5lac% (ox testing tests 5RS & SRS
$esting external interfacing is 5lac% (ox testing
$esting internal interfacing is ;hite (ox testing
;hite (ox testing is done w.r.t design documents
+
Testing:
< $est plan is deeloped (ased on 0eelopment plan
7ormula for test efficiency# 0RE = ' / ' > 5
0RE = 0efect Remoal Efficiency
' 5ugs found at the testing side
5 5ugs found at the client side
0RE= ?.@ A ?.B good
?.C A ?.@ requires improement
D ?.C poor
"efinement #orm of $%Mo&el
.
7rom the a(oe refinement form of E"Model, small & medium scale organiFations are maintaining
separate testing team for 7unctional & System testing stage.
'( "eviews &uring Analysis
*n general, Software deelopment process starts with *nformation Gathering & 'nalysis. *n this stage
5usiness 'nalyst category people are preparing 5RS & S/w RS documents and after completion documents
preparation, they conduct reiews on the documents for completeness & correctness.
$his reiew focuses on (elow factors#
+, 're they complete
., 're they met with right requirements of client / customer
/, 're they achiea(le w.r.t technology
1, 're they reasona(le w.r.t time & cost
3, 're they testa(le
)( "eviews &uring Design
'fter completion of 'nalysis phase & their reiews, our 2ro)ect"leel designers will start logical design
of application in terms of External & *nternal design 6890:s & 990:s,. *n this stage, they conduct reiews for
completeness & correctness of designed documents.
$his reiew focuses on (elow factors#
+, 're they understanda(le
., 're they met with right requirements of client / customer
/, 're they complete
1, 're they follow a(le
3, 0oes they handle errors
*( During +nit Testing
'fter completeness of 0esign & their reiews, software programmers will starts coding the logical
design to physical construction of software. 0uring these coding stage programmers is conducting Hnit $esting
through a set of ;hite (ox testing techniques, Hnit $esting also %nown as Module / Component / 2rogram /
Micro testing
,!ite -o. Testing:
$here are three possi(le ;hite (ox testing techniques
+, Execution $esting
5asic path coerage A Execution of all possi(le (loc%s in a program
9oops coerage A $ermination of loop statements
2rogrammer technique coerage A less no of memory cycles & C2H cycles
., Iperation $esting A Running the application on Customer expected platforms
/, Mutation $esting
Mutation means that a change program. ;hite (ox testers are performing the change in the program to
estimate test coerage on that program. Mutation testing can decide whether the test coerage is correct or
wrong
1, *ntegration $esting
'fter completion of dependent modules of deelopment & testing, 2rogrammers com(ine them to form
a System. *n this *ntegration, they are conducting *ntegration testing on the compiled modules w.r.t 890. $here
are three approaches to conduct *ntegration testing
/
Top%Down Approac!
*n this approach, testing is conducted on Main module without conducting testing to some of su("
modules. 7rom the a(oe diagram, a Stu( is a temporary program instead of under constructie su("module, it
is %nown as called program.
/ottom%+p Approac!
*n this approach, testing is conducted on su("modules without conducting testing on main modules.
7rom the a(oe diagram, a 0rier is a temporary program instead of main module, it is %nown as calling
program.
San&wic! / 0y-ri& Approac!
*n this approach, testing is conducted ta%ing (oth $op"0own & 5ottom 'pproaches.
1
< 5uild# ' finally integrated all modules set <.exe form file is called (uild.
1( #unctional 2 System testing 34 imp(
'fter completion of final integration of modules as a system, $esting Engineers are planning to conduct
7unctional & System testing through 5lac% (ox testing techniques, these techniques classified into four
categories.
+, Hsa(ility $esting
., 7unctional $esting
/, 2erformance $esting
1, Security $esting
7rom '(oe + & . are Core leel and / & 1 are 'dance leel
0uring Hsa(ility testing, testing team alidates Hser"7riendliness of screens.
0uring 7unctional testing, $$ alidates the correctness of customer requirements
0uring 2erformance testing, $$ estimates speed of processing
0uring Security testing, $esting team alidates priacy to Hser operations
'( +sa-ility Testing
*n general, $$ starts with test execution with Hsa(ility testing. 0uring test, testing team alidates Hser"
7riendliness of screens of (uild. 0uring Hsa(ility testing, $$ applies two types of su("test#
a, Hser *nterface $est
Easy of use 6Hnderstanda(le screens,
9oo% & 7eel 6'ttractieness & 2leasantness,
Speed in *nterface 69ess no of eent to complete a test, easy short naigation,
(, Manual Support $est
Context sensitieness of user manuals
Manual support test are conducted at the end of all testing & (efore release
)( #unctional Testing
$he ma)or part of 5lac% (ox testing is 7unctional testing, during this test, $esting team+ concentrates on
Jmeet customer requirementsK. $his 7unctional $esting is classified into (elow su("test.
a, 7unctional / Requirement $esting
3
0uring this test, $est Engineers alidates correctness of eery functionality in terms of (elow
coerage:s.
5ehaioral coerage 6changes in o()ect properties,
*nput domain coerage 6siFe & type of eery input & output o()ect,
Error handling coerage 6preenting negatie naigations,
Calculations coerage 6correctness of output,
5ac%"end coerage 6impact of 7ront"end operation on (ac%"end ta(les contents,
Serice leels coerage 6order of functionalities,
(, *nput 0omain $esting
*t is a part of 7unctionality testing- $est Engineers are maintaining special structures to define siFe &
type of input o()ect
c, Recoery $esting
*t is also %nown as Relia(ility testing. 0uring this test, $esting team alidates whether the application is
changing from a(normal state to normal state or not.
d, Compati(ility $esting
*t is also %nown as 2orta(ility testing. 0uring this test, $esting team alidates whether application (uild
run on customer expected platforms or not. 0uring this test, $esting Engineers are finding (ac%ward
compati(ility at maximum.
7orward compati(ility application is ready to run (ut Iperating system is not supporting.
5ac%ward compati(ility Iperating system is supporting (ut the application has some internal coding
pro(lems to run on Iperating system
e, Configuration $esting
*t is also %nown as 8ardware compati(ility testing. 0uring this test, $esting team alidates whether
application (uild supports different technology 8ardware deices or not.
f, *nter"Systems $esting
0uring this test, $esting team alidates whether application (uild co"existence with other existing
software:s or not and also test whether any 0ead loc% situation occurs or not.
g, *nstallation $esting
0uring this test, testing team alidates whether application (uild along with supported software:s into
customers site li%e configured systems. 0uring this test, testing team o(seres (elow factors.
Setup program execution to start installation
Easy *nterface
'mount of dis% occupied after installation
h, 2arallel / Comparatie $esting
0uring this test, testing team compares application (uild with competitie products in mar%et.
i, Sanitation / Gar(age $esting
0uring this test, testing team tries to find extra features in application (uild w.r.t customer requirements.
< 0efects
0uring this test, testing team reports defects to deelopers in terms of (elow categories
+. Mismatches (etween expected & actual
.. Missing functionality
/. Extra functionality w.r.t customer requirement
4
< Manual /s 'utomation
' $ester conducts any test on application (uild without using any testing tool is called Manual testing, if
any testing tool is used then it is called 'utomation testing
*n common testing process, $esting Engineers are using test 'utomation w.r.t test impact & criticality.
*mpact test repetition & Criticality complex to apply test manually. 0ue to these two reasons testing
people are using test 'utomation.
), Re"testing
$he re"execution of a test with multiple test data to alidate a function, e.g. $o alidate multiplication,
$est Engineers use different com(inations of input in terms of min, max, "e, >e, Fero, int, float, etc.
%, Regression $esting
$he re"execution of test on modified (uild to ensure (ug fixing wor% & occurrence of any side effects,
$est Engineers conducts this test using 'utomation
l, Error, 0efect & 5ug
' mista%e in code is Error, due to errors in coding, $est Engineers are getting mismatches in application
(uild are defects, if the defects are accepted (y deelopers to (e soles then it is 5ug.
Testing Documents
C
'(oe 7igure, shows the arious leels of documents prepared at pro)ect testing. $est 2olicy is documented (y
&uality Control. $est Strategy & $est Methodology are documented (y &uality 'nalyst or 2ro)ect Manager.
$est 2lan, $est Cases, $est 2rocedure, $est Script & 0efect Report are documented (y &uality 'ssurance
Engineers or $est Engineers.
$est 2olicy & $est Strategy are Company 9eel 0ocuments. $est Methodology, $est 2lan, $est Cases, $est
2rocedure, $est Script, 0efect Report & 7inal $est Summary Report are 2ro)ect 9eel 0ocuments.
'( T5ST P6LC7:
$his document deeloped (y &uality Control people 6Management,. *n this document &uality Control
defines J$esting I()ectieK.
Test Policy Document
A&&ress of t!e Company
Test Definition : Eerification & Ealidation
Testing Process : 2roper planning (efore starts testing
Testing Stan&ar&s : Ine defect per .3? lines of code or +? 72 67unctional points,
Testing Measurements : &'M, $$M, 2CM
<<<<<<< 6C.E.I,
&'M# &uality 'ssurance Measurements, how much quality is expected
$$M# $esting $eam Measurements, how much testing is oer & is yet to complete
2CM# 2rocess Capa(ility Measurements, depends on old pro)ect to the upcoming pro)ects.
)( T5ST ST"AT587:
$his is a Company leel document & deeloped (y &uality 'nalyst or 2ro)ect Manager Category
people, it defines J$esting 'pproachK.
Components:
a, Scope & I()ectie# 0efinition & purpose of testing in organiFation
(, 5usiness *ssue# 5udget control for testing
c, $est 'pproach# Mapping (etween deelopment stages & $esting *ssue.
d, $est 0eliera(les# Required testing documents to (e prepared
e, Roles & Responsi(ilities# !ames of the )o( in testing team & their responsi(ilities
f, Communication & Status reporting# Required negotiation (etween testing team & deeloping team
during test execution
g, 'utomation & $esting $ools# 2urpose of automation & possi(ilities to go to test automation
h, $esting Measurements & Metrics# &'M, $$M, 2CM
i, Ris%s & Mitigation# 2ossi(le pro(lems will come in testing & solutions to oercome
), Change & Configuration Management# $o handle change request during testing
%, $raining 2lan# Required training sessions to testing team (efore start testing process
Testing Issues:
+. 'uthoriFation# ;hether user is alid or not to connect to application
.. 'ccess Control# ;hether a alid user hae permission to use specific serice
/. 'udit $rail# Maintains metadata a(out user operation in our application
1. Continuity of 2rocessing# *nter"process communication
3. Correctness# Meet customer requirement in terms of functionality
4. Coupling# Co"existence with other existence software to share resources
C. Ease of Hse# Hser 7riendliness of the screens
@. Ease of Iperator# *nstallation, Hn"installations, 0umping, Hploading, 0ownloading, etc.,
@
B. 7ile *ntegrity# Creation of (ac%up
+?. Relia(ility# Recoer from a(normal state
++. 2erformance# Speed of processing
+.. 2orta(le# Run on different platforms
+/. Serice leels# Irder of functionalities
+1. Maintaina(le# ;hether our application (uild is long term sericea(le to our customer
+3. Methodology# ;hether our tester are following standards or not during testing
*( T5ST M5T06D6L687:
*t is pro)ect leel document. Methodology proides required testing approach to (e followed for current
pro)ect. *n this leel &uality 'nalyst select possi(le approach for corresponding pro)ect testing.
Pet Process:
2rocess inoles experts, tools & techniques. *t is a refinement form of E"Model. *t defines mapping
(etween deelopment & $esting stages. 7rom this model, IrganiFations are maintaining separate team for
7unctional & System testing & remaining stages of testing done (y deelopment people. $his model is
deeloped in 8C9 & recogniFed (y &' 7orum of *!0*'.
B
T5ST98 P"6C5SS
+?
1( T5ST PLA9998:
++
'fter finaliFation of possi(le test for current pro)ect, $est 9ead category people concentration on test
plan document preparation to define wor% allocation in terms of ;hat, ;ho, ;hen & 8ow to test. $o prepare
test plan document, test plan order follows (elow approach-
': Team #ormation:
*n general, $est planning process starts with testing team formation. $o define a testing team, test plan
author depends on (elow factors-
+. 'aila(ility of testers
.. $est duration
/. 'aila(ility of test enironment resource
): &entify Tactical "is;:
'fter testing team formation 2lan author analysis possi(le & mitigation 6ad hoc testing,
L Ris% +# 9ac% of %nowledge of $est Engineer on that domain
L Sol
n
+# Extra training to $est Engineers
L Ris% .# 9ac% of Resource
L Ris% /# 9ac% of (udget Mless no of timeN
L Sol
n
/# *ncrease $eam siFe
L Ris% 1# 9ac% of $est data
L Sol
n
1# Conduct test on past experience (asis i.e., ad hoc testing or contact client for data
L Ris% 3# 9ac% of deeloper process rigor
L Sol
n
3# Report to $est 9ead for further communication (etween test & deelopment 2M
L Ris% 4# 0elay of modified (uild deliery
L Sol
n
4# Extra hours of wor% is needed
L Ris% C# 9ac% of communication in (etween $est Engineer $est team and
$est team 0eelopment team
*: P"5PA"5 T5ST PLA9:
'fter completion of testing team formation & Ris% analysis, $est plan author concentrate on Test Plan
Document in *EEE format.
+. $est 2lan *0# Hnique !o or !ame e.g. S$2"'$M
.. *ntroduction# '(out 2ro)ect description
/. $est *tems# Modules / 7unctions / Serices / 7eatures / etc.
1. 7eatures to (e tested# Responsi(le Modules for $est design 6preparing test cases for added modules,
+.
3. 7eatures not to (e tested# ;hich feature is not to (e tested and ;hyO 60ue to test cases aaila(le for
the old modules, so for these modules no need to (e tested / no test case
Above (3), (4) & (5) decides which module to be tested !h"t to test#
4. 'pproach# 9ist of selected testing techniques to (e applied on a(oe specified modules in reference to
the $RM 6$est Responsi(le Matrix,.
C. 7eature pass or fail criteria# ;hen a feature is pass or fail description 6Enironment is good, 6'fter
testing conclusion,
@. Suspension criteria# 2ossi(le a(normal situations rose during a(oe features testing 6Enironment is
not good, 60uring testing conclusion,
B. $est Enironment# Required software & 8ardware to (e tested on a(oe features
+?. $est 0eliera(les# Required testing document to (e prepared 6during testing, the types of documents
are prepared (y tester,
++. $esting $as%# !ecessary tas%s to do (efore start eery feature testing
Above ($) to (%%) speci&ies ' (ow to test#
+.. Staff & $raining# !ames of selected $est Engineers & training requirements to them
+/. Responsi(ilities# ;or% allocation to eery mem(er in the team 6dependa(le modules are gien to single
$est Engineer,
+1. Schedule# 0ates & $imes of testing modules
Above (4) speci&ies !hen to test#
+3. 9ist & Mitigation# 2ossi(le testing leel ris%s & solution to oercome them
+4. 'pproals# Signatures of $est plan authors & 2ro)ect Manager / &uality 'nalyst
1( "eview Test Plan:
'fter completion of plan document preparation, $est plan author conducts a reiew of completion &
correctness. *n this reiew, 2lan author follows (elow coerage analysis
5RS (ased coerage 6;hat to testO Reiew,
Ris%s (ased coerage 6;hen & ;ho to testO Reiew,
$RM (ased coerage 68ow to testO Reiew,
<( T5ST D5S8998:
'fter completion of $est 2lanning & required training to testing team, corresponding testing team
mem(ers will start preparing the list of test cases for their responsi(le modules. $here are three types of test
cases design methods to coer core leel testing 6Hsa(ility & 7unctionality testing,.
a, 5usiness 9ogic (ased test case design 6S/w RS,
(, *nput 0omain (ased test case design 6E"R diagrams / 0ata Models,
c, Hser *nterface (ased test case design 6MS";indows rules,
a( /usiness Logic -ase& Test Case &esign 3S/w "S(
*n general, $est Engineers are preparing a set of $est Cases depends on Hse Cases in 6S/w RS,. Eery
Hse Case descri(es a functionality in terms of inputs, process & output, depends on this Hse Cases $est
Engineers are preparing $est Cases to alidate the functionality
+/
7rom the a(oe model, $est Engineers are preparing $est Cases depends on corresponding Hse Cases & eery
test case defines a test condition to (e applied.
$o prepare test cases, $est Engineers studies Hse Cases in (elow approach#
Steps#
+, Collect Hse Cases of our responsi(le module
., Select a Hse Case & their dependencies from the list
..+, *dentify entry condition 65ase state,
..., *dentify input required 6$est data,
../, *dentify exit condition 6End state,
..1, *dentify output & outcome 6Expected,
..3, *dentify normal flow 6!aigation,
..4, *dentify alternatie flows & exceptions
/, ;rite $est Cases depends on a(oe information
1, Reiew $est Cases for the completeness & correctness
3, Goto step 6., until completion of all Hse Cases completion
Hse Case *#
' login process allows user id & password to alidate users. 0uring these alidations, login process
allows user id in alpha"numeric from 1 to +4 characters long & password in alpha(ets in lowercase from 1 to @
characters long.
Case study#
$est Case +, Successful entry of user id
+1
$est Case 7ormat#
0uring $est design $est Engineers are writing list of $est Cases in *EEE format.
?+, $est Case *0# Hnique no or name
?., $est Case !ame# !ame of test condition to (e tested
?/, 7eature to (e tested# Module / 7unction / 7eature
?1, $est suit *0# 5atch *0, in which this case is mem(er
?3, 2riority# *mportance of $est Case M9ow, Med, 8ighN
2
?
5asic functionality
2
+
General functionality 6*/2 domain, Error handling, Compati(ility etc,,
2
.
Cosmetic testing 6H*$,
?4, $est Enironment# Required Software & 8ardware to execute
?C, $est afford 6person / hr,# $ime to execute this $est Case e.g. .? minutes
?@, $est duration# 0ate & $ime
?B, $est Setup# Required testing tas% to do (efore starts case execution 6pre"requisites,
+?, $est 2rocedure# Step (y step procedure to execute $est Case
++, $est Case passes or fails criteria# ;hen this case is pass or fail
!ote# $est Engineers follows list of $est Cases along with step (y step procedures only
+3
Example +#
2repare $est 2rocedure for (elow test cases JSuccessful file sae operation in !otepad J.
Ste
p
9o
Action nput
"e=uire&
5.pecte&
+ Ipen !otepad Empty Editor
. 7ill with text Sae *con ena(led
/ Clic% Sae *con or clic% 7ile
menu
Iption & select sae option
Sae 0ialog (ox appears with
0efault file name
1 Enter 7ile name & Clic% Sae Hnique
7ile name
7ocus to !otepad & 7ile
name
'ppears in title (ar of
!otepad
9ote: #or more e.amples refer to notes
-( nput Domain -ase& Test Case &esign 35%" &iagrams / Data Mo&els(
*n general, $est Engineers are preparing maximum $est Cases depends on Hse Cases or functional
requirements in S/wRS. $hese functional specifications proide functional descriptions with input, output &
process, (ut they are not responsi(le to proide information a(out siFe & type of input o()ects. $o correct this
type of information, $est Engineers study 0ata model of responsi(le modules E"R diagram. 0uring 0ata model
study, $est Engineer follows (elow approach# Steps#
+, Collect 0ata model of responsi(le modules
., Study eery input attri(ute in terms of siFe, type & constraint
/, *dentify critical attri(utes in the test, which is participated in manipulation & retrials
1, *dentify non"critical attri(utes such as input & output type
3, 2repare 5E' & EC2 for eery input o()ect
5CP /$A3Si>e / "ange(
nput
Attri-ute
$ali
&
nvali
&
Minimu
m
Ma.imum
Pxxx xxxx xxxx xxxx xxxx
J J J J J
J J J J J
J J J J J
DATA MAT"?
+4
!ote# *n general, $est Engineers are preparing step (y step procedure (ased $est Cases for functionality
testing. $est Engineers prepare alid / inalid ta(le (ased $est Cases for input domain of o()ect testing M0ata
Matrix N
9ote: #or e.amples refer to notes
c( +ser nterface -ase& test case &esign 3MS%,in&ows rules(
$o conduct Hsa(ility $esting, $est Engineers are preparing list of $est Cases depends on our
organiFation Hser *nterface standards or conentions, Glo(al Hser *nterface rules & interest of customer site
people.
Example# $est Cases
+, Spelling chec%
., Graphics chec% 6Screen leel 'lign, 7ont style, Color, SiFe & Microsoft six rules,
/, Meaning of error messages
1, 'ccuracy of data displayed
3, 'ccuracy of data in the data(ase are result of user inputs, if deeloper restrict the data in
data(ase leel (y rounding / truncating then the deeloper must also restrict the data in
front"end as well
4, 'ccuracy of data in the data(ase as the result of external factors. Ex. 7ile attachments
C, Meaningful help messages 6Manual support testing,
Reiew $est Cases#
'fter completion of all possi(le $est Cases preparation for responsi(le modules, $esting team
concentrates on reiew of $est Cases for completeness & correctness. *n this reiew, $esting team applies
coerage analysis.
$est Case Reiew
+, 5R (ased coerage
., Hse Cases (ased coerage
/, 0ata model (ased coerage
1, Hser *nterface (ased coerage
3, $RM (ased coerage
't the end of this reiew, $est 9ead prepare Requirement $racea(ility Matrix or Requirement
Ealidation Matrix 6R$M / REM,
+C
7rom R$M / REM model, it defines mapping (etween customer requirement & prepared $est Cases to
alidate the requirement.
@( T5ST 5?5C+T69:
'fter completion of $est Cases selections & their reiew, $esting team concentrate on 5uild release
from deelopment side & $est execution on that (uild.
a( Test 5.ecution Levels or P!ases:
See figure in next page for clear understanda(ility of this leels
-( Test 5.ecution Levels v/s Test Cases:
9eel A ? 2
?
$est Cases
9eel A + 'll 2
?
, 2
+
& 2
.
$est Cases as (atches
9eel A . Selected 2
?
, 2
+
, & 2
.
w.r.t modification
9eel A / Selected 2
?
, 2
+
, & 2
.
w.r.t critical areas in the master (uild
+@
c( /uil& $ersion Control:
*n general, $esting Engineers are receiing (uild from deelopment in (elow model
0uring $est execution $est Engineer are receiing modified (uild from software. $o distinguish old &
new (uilds, deelopment team maintains unique ersion in system, which is understanda(le to $ester / $esting
team. 7or this ersion controlling deelopers are using ersion control tools 6Eisual Source Safe,
&( Level A B 3Sanity / Test Acceptance / /uil& verification test(:
'fter receiing initial (uild, $esting Engineers concentrate on (asic functionality of that (uild to
estimate sta(ility for complete testing. *n this Sanity testing, $esting Engineers tries to execute all 2
?
$est Cases
to coer (asis functionality. *f functionality is not wor%ing / functionality missing, testing team re)ects that
(uild. *f $ester decided sta(ility then they concentrate on $est execution of all $est Cases to detect defects.
0uring this Sanity testing, $esting Engineer o(seres (elow factors on that (uild
+, Hnderstanda(le
., Iperata(le
/, I(sera(le
1, Consistency
3, Controlla(le
4, Simplicity
+B
C, Maintaina(le
@, 'utomation
7rom the a(oe J@K testa(le issues, Sanity test is also %nown as $esta(ility testing / IC$ angle testing.
e( Test Automation:
*f test automation is possi(le than $esting team concentrate on $est script creation using corresponding
testing tools. Eery $est script consists of naigation statement along with required chec% points.
f( Level A ' 3Compre!ensive testing(
'fter completion of Sanity testing & possi(le test automation, testing team concentrates on test (atches
formation with depended $est Cases. $est (atches are also %nown as $est suits / sets. 0uring these $est (atches
execution, $est Engineers prepare test log document, this document consist of three types of entries.
+, 2assed 6Expected = 'ctual,
., 7ailed 6'ny one Expected Q= 'ctual, 'ny one Expected ariants from 'ctual,
/, 5loc%ed 6Corresponding parent functionality failed,
g( Level A ) 3"egression testing(
0uring Comprehensie test execution, $est Engineers are reporting mismatches as defects to deelopers.
'fter receiing modified (uild from deelopers, $est Engineers concentrate on Regression testing to ensure
(ug"fixing wor% & occurrences of side effects.
.?
Case *#
*f deelopment team resole (ugs seerity which is high, $est Engineers re"execute all 2
?
, 2
+
&
carefully selected 2
.
$est Cases on modified (uild
Case **#
5ugs seerity is medium, then all 2
?
, carefully selected 2
+
& some of 2
.
$est Cases
Case ***#
5ugs seerity is low, then some 2
?
, 2
+
& 2
.
Case *E#
*f deelopment team released modified (uild due to sudden changes in pro)ect requirement then $est
Engineers re"execute all 2
?
, 2
+
& carefully selected 2
.
$est Cases w.r.t that requirement modification.
!( Level A * 3#inal "egression / Pre%Acceptance testing(
C( T5ST "5P6"T98:
0uring comprehensie testing, $est Engineer is reporting mismatches as defects to deelopers through
*EEE format.
+, 0efect *0# Hnique !o or !ame
., 0escription# Summary of the defect
/, 7eature# Module / 7unction / Serice , in these module $E found the defect
1, $est Case !ame# Corresponding failing test condition
3, Reproduci(le 6Res / !o,# Res Eery time defect appears during test execution
!o Rarely defect appears
.+
4, *f Res, attach test procedure#
C, *f !o, attach snapshot & strong reasons#
@, Status# !ew / Reopen
B, Seerity# Seriousness of defect w.r.t functionality 6high / medium / low,
+?, 2riority# *mportance of the defect w.r.t customers 6high / medium / low,
++, Reported (ug# !ame of $est Engineer
+., Reported on# 0ate of su(mission
+/, 'ssign to# !ame of the responsi(le person in deelopment team "S 2M
+1, 5uild Eersion *0# *n which (uild, $est Engineer fount the defect
+3, Suggested fix 6Iptional,# $ester tries to produce suggestion to sole this defect
0efect 'ge# $he time gap (etween Jreported onK & Jresoled onK
0efect su(mission process#
0eferred 'ccepted (ut not interested to resole in this ersion
0efect Resolution#
'fter receiing defect report from $esters, deelopers reiew the defect & they send resolution type to
$ester as a reply
+, 0uplicate, re)ected due to the defect is same as preiously reported defect
., Enhancement, re)ected due to the defect is related future requirement of customer
/, 8/w limitation, re)ected due to the defect raised w.r.t limitation of 8/w deices
1, S/w limitations, re)ected due to the defect raised w.r.t limitation of S/w $echno
3, !ot applica(le, re)ected due to the defect has no proper meaning
4, 7unctions as designed, re)ected due to coding is correct w.r.t to designed doc:s
C, !eed more information, not 6accepted / re)ected, (ut deelopers requires extra information to
understand the defect
@, !ot reproduci(le, not 6accepted / re)ected, (ut deelopers require correct procedure to reproduce the
defect
B, !o plan to fix it, not 6accepted / re)ected, (ut deelopers want extra time to fix
+?, 7ixed, deelopers accepted to resole
..
++, 7ixed indirectly, accepted (ut not interested to resole in this ersion 6default,
+., Hser misunderstanding needs extra negotiation (etween testing & deelopment team.
$ypes of defects#
?+, Hser *nterface (ugs 6low seerity,#
+, Spelling mista%es 6high priority,
., *mproper alignment 6low priority,
?., 5oundary related (ugs 6medium seerity,
+, 0oesn:t allows alid type 6high priority,
., 'llows inalid type also 6low priority,
?/, Error handling (ugs 6medium seerity,
+, 0oesn:t proiding error message window 6high priority,
., *mproper meaning of error message 6low priority,
?1, Calculations (ugs 6high seerity,
+, 7inal output is wrong 6low priority,
., 0ependent results are wrong 6high priority,
?3, Race condition (ugs 6high seerity,
+, 0ead loc% 6high priority,
., *mproper order of serices 6low priority,
?4, 9oad conditions (ugs 6high seerity,
+, 0oesn:t allow multiple users to access / operate 6high priority,
., 0oesn:t allow customers accepted load 6low priority,
?C, 8ardware (ugs 6high seerity,
+, 0oesn:t handle deice 6high priority,
., ;rong output from deice 6low priority,
?@, *0 control (ugs 6medium seerity,
+, 9ogo missing, wrong logo, Eersion !o mista%e, Copyright window missing,
0eelopers !ame missing, $ester !ame missing
?B, Eersion control (ugs 6medium seerity,
+, 0ifferences (etween two consecutie (uild ersions
+?, Source (ugs 6medium seerity,
+, Mista%e in help documents A Manual support
D( T5ST CL6S+"5:
'fter completion of all possi(le test cycle execution, $est 9ead conducts a reiew to estimate the
completeness & correctness of testing. *n this reiew, $est 9ead follows (elow factors with $est Engineers
+, Coerage 'nalysis
a, 5R (ased coerage
(, Hse Cases (ased coerage
c, 0ata model (ased coerage
d, Hser *nterface (ased coerage
e, $RM (ased coerage
., 5ug density
a, Module ' has .?T percentile (ugs found
(, Module 5 has .?T percentile (ugs found
c, Module C has 1?T percentile (ugs found
d, Module 0 has .?T percentile (ugs found
./
/, 'nalysis of deferred (ugs
;hether deferred (ugs are deferra(le or not
't the end of this reiew, $esting team concentrate on high (ug density modules or all modules if time
is aaila(le.
E( +ser Acceptance Testing 3+AT(
IrganiFation management concentrate on H'$ to collect feed(ac%, there are two approaches to conduct
testing.
+. 'lpha 6U, test
.. 5eta 6V, test
'B( Sign 6ff
'fter completion of Hser 'cceptance testing & their modifications, $est 9ead concentrates on final test
summary report creation. *t is a part of Software Release !ode 6S/w R!,. $his final test summary report consist
of (elow documents
+, $est Strategy / Methodology 6$RM,
., System $est 2lan
/, Requirement $racea(ility Matrix 6R$M,
1, 'utomated $est Scripts
3, 5ugs Summary Reports
$he (elow, has to (e in horiFontal direction
5ug 0escription
7eature
7ound 5y
Status 6closed / deferred,
Comments
.1
CAS5 ST+D7 69 A P"6F5CT T5ST98 P"6C5SS
$he J P K is a client/serer product. *t is running in single computer with windows .??? as IS this product
proides a facility to search matched records in existing data(ase. w.r.t has gien search %eys.
$his product maintains a default administrator to create new users and eery alid user search data in data(ase.
'ctiity flow diagram# "
.3
7H!C$*I!'9 2I*!$S# "
9ogin is ta%ing user id and password
Hser id and password allows alpha(ets in lower case from 1 to @ characters long.
!ew user id:s created (y administrators only
!ew user creation windows allows unique user id and password with create and cancel (uttons
JSearch recordsK opened for alid users only
JSearch records windowK maintains (elow search %eys
Customer id# 4 digits num(er 6collected from design document
7irst name# one character in upper or lower
9ast name# one to eight characters in lower case characters
0ate of (irth# ddWmmWyy in numeric
'ge# JfromK and JtoK in numeric
Search records windows allows (elow com(ination of fields to search records.
9ast name
9ast with first name
9ast name with first name and d"o"(
9ast name with first name and age
Customer id only
JSearch recordsK window consists of Jstart searchK and Jstop searchK (uttons.
'llows last name as full or partial
'llows customer id as full or partial with < or wild card
Customer id

Refresh search records window using 'lt>ctrl
0isplay matched records in a pop"up window with o% (utton after search completion.
.4
Returns message li%e Jtoo many matches to display when matched records S+???
$est methodology#" 6(y 2M,
$esting stage System testing
$esting 7actors
'uthoriFation X
'ccess Control X
'udit trail Y
Continuity to X
Correctness X
Coupling Y
0ata integrity X
Ease of use X
Ease of operate X
Relia(ility X
7orta(le Y
2erformance Y
Serice leels X
Maintaina(le X
Methodology X
!ote# $est responsi(ility matrix for **P* 6++ (y +,
JPK product is maintaining metadata so
it is not sharing resources of other application
$his application went to run on windows .???
*t is a stand alone application 6at time one user can operate,
So need net to test load and stress testing,
System test plan (y test lead#"
+. $est plan *0# S$2ZP
.. *ntroduction# JPK is a product and it proides a facility to connect to existing data (ase and search
matching records to retriee.
/. $est items user creation
9ogin (y user
Search records
1. 7eatures to (e tested# user creation
9ogin (y user
Search records
3. 7eatures not to (e tested#"
4. 'pproach# $o apply 2M selected + factor from $RM, (elow (lac% (ox testing techniques are suita(le to
follow depends on test lead.
Hser interface testing
Manual support testing
7unctionality testing
i/p domain testing
Recoery testing
Sanitation testing
.C
*nstallation testing
Security testing
Complaints testing
C. Entry criteria# "
're the necessary documents aaila(leO
*s the JPK product is ready for release from deelopersO
*s the supporting data(ase aaila(le to search required recordsO
*s the test enironment readyO
@. Suspension criteria#
0ata (ase disconnect may require suspension of testing
Suspension of testing is mandatory when searching records process went to infinite.
'dmin is failed to new user creation, a decision can (e mad to continue testing on Jsearching
recordsK module using admin or other existing alid users.
B. Exit Criteria# "
Ensure that the JPK product proides the required serices
Ensure that all test documents has (een completed up to date.
'll high seerity (ugs resoled.
++. $est enironment#"
Client pc or local host
IS# ;in.???
05 serer# IR'C9E/ S&9 SEREER/ MS"'CCESS
Connectiity# 0S!/ $hin 0riers
+.. $esting $as%s#"
'aila(ility of admin with password
0ata(ase consists of records
Ealid users are a(le to data(ase to search records
+/. Staff and $raining needs#"
$est Engg.. / &' Engg# [urugonda Srinaiah
+1. Responsi(ilities#
0ocument / Report Responsi(ility Effort
+. $st cases with procedures [.Srinaiah +. hours
0efect Report [ Srinaiah eery day during $esting
.@
$est completion reports $est 9ead with 't the end of the $esting
[ Srinaiah
+3. Schedule#
$as% Effort Start date End date
$est design +. hours .@"+.".??3 .B"+.".??3
*mplement test and 1 hours .B"+.".??3 .B"+.".??3
Reiew
Execute test .1 hours /?"+.".??3 ?+"?+".??4
Ealuate test @ hours ?."?+".??4 ?."?+".??4
+4. Ris%s and mitigations#"
+. 9ac% of documentation#
Contact (usiness analyst
'd"hoc testing
Contact customer site people if possi(le
.. 9ac% of time
Ier"time
/. 0elays and deliery#
Ier time
1. 9ac% of deelopment process reggur#
Contact test lead to motiate deelopers
Ier time to complete tas% is right time
+C. '22RIE'9S# "
$est case +#
Signature of 2M and signature of test lead.
$est case .# Successful entry of user id
5E' 6siFe,
""""""""""""""""""""""""""""""""""""
Min = 1 chars pass
Max = @ chars pass
Min"+ =/ chars fail
Min >+ = 3 chars pass
Max A+ = C chars pass
Max >+ = B chars fail
$est case /# successful entry of password
5E' 6siFe,
"""""""""""""""""""""""""""""""
.B
Min = 1 chars pass
Max = @ chars pass
Min A+ = / chars fail
Min >+ = 3 chars pass
Max > = C chars pass
Max = B chars fail
$est case 1# successful login operation
Hser id 2assword Criteria
'dmin alid pass
'dmin inalid fail
Ither alid alid pass
Ither alid inalid fail
Ither inalid inalid fail
5lan% alue fail
Ealid (lan% fail
$est case 3# Successful selection of new user creation option
$est case 4# Hn successful selection of this option due to current user is not admin.
$est case C successful entry of user id in create user window
!ote# 6li%e as $est case.,
$est case @# Successful entry of userid in create user window
!ote# 6"""""""""""test case /,
$est caseB# Successful creation of new user (y admin
$est case+?# unsuccessful new user creation due to gien user id is not unique.
$est case ++# successful closing of new user creation window using cancel
6'fter enter user id and offer enter passes,
$est case +.# Successful selection of search records option
$est case +/# successful entry of customer id
5E' 6siFe, EC2 6$R2E,
Min = max = 4 alid inalid
""""""""""""""""""""""""""""""""""""""""""""""""""""
? A B a"F, '"\, special characters
Expect <, (lan% space
Start with <
Exp# +./ GH 4)*IH '<./P
/?
$est case +1# successful entry of first name
Min = max = + pass Ecp
"""""""""""""""""""""""""""""""""""
o X fail alid inalid
"""""""""""""""""""""""""""""""""""
a" F o"B,
'"\ special characters
$est case +3# successful entry of last name#
Min = + and max = @ pass """"""""""""""""""""""""""""""""""
alid inalid
""""""""""""""""""""""""""""""""""
a" F '"\, o"B,
Special characters
$est case +4# successful entry of 0I5
5E' 6range,
Ecp 6type,
0ay# min ?+ """""""""""""""""
min /+ alid inalid
"""""""""""""""""
?" B a"F, '"\
Month# min ?+ special characters
max +.
Rear# min ??
max BB
Case +C# success entry of age from
Ecp6type,
min ?+ """""""""""""""""
max .. alid inalid
"""""""""""""""""
?" B a"F, '"\
Special characters
$est case +@# successful entry of age to
!ote# li%e as a(oe
$est case +B# successful display of matched records with full last name and all other fields are (lan%
$est case .?# successful display of matched records with full last name and first name
$est case.+# successful display of matched records with full last name first name and do(
$est case..# successful display of matched records with full last name first name age
/+
$est case ./# on successful search operation due to inalid com(ination of filled fields.
$est case .1# unsuccessful search operation due to inalid 0o(
$est case .3# unsuccessful search operation due to age from greater than age ]$o:
$est case.4# successful display of records with search %ey as partial last name and other fields as (lan%
$est case .C# successful display of records with search %ey a partial last name and first name
$est case .@# successful display of records with search %ey as partial last name, first name and 0o(
$est case .B# successful display of records with search %ey as partial last name, first name
$est case /?# successful display of records with search %ey as customer id
$est case /+# successful display of records with search %ey as partial customer id with < as wild card
$est case /.# Hnsuccessful display of records due to no matching records in data(ase w.r.to gien search %eys
$est case //# unsuccessful display of records due to Jtoo manyK records to display when no of matched records
greater than +???
$est case /1# successful refresh search window with 'lt >Ctrl
$est case /3# Successful termination of search operation when clic% Jstop searchK (utton.
$est case /4# successful closing of records window through clic% o.% after searching.
$est case 1?# Meaningful help messages and error messages
/.