Srihari Techsoft

Software Testing
Software Testing
An overview
An overview

Srihari Techsoft
Introduction & Fundamentals
Introduction & Fundamentals
What is Software Testing?
What is Software Testing?
Why testing is necessary?
Why testing is necessary?
Who does the testing?
Who does the testing?
What has to be tested?
What has to be tested?
When is testing done?
When is testing done?
How often to test?
How often to test?

Srihari Techsoft
Most Common Software problems
Most Common Software problems

Incorrect calculation
Incorrect calculation

Incorrect data edits & ineffective data

Incorrect data edits & ineffective data
edits
edits

Incorrect matching and merging of data

Incorrect matching and merging of data

Data searches that yields incorrect

Data searches that yields incorrect
results
results

Incorrect processing of data

Incorrect processing of data
relationship
relationship

Incorrect coding / implementation of

Incorrect coding / implementation of
business rules
business rules

Inadeuate software performance

Inadeuate software performance

Srihari Techsoft

Confusing or misleading data

Software usability by end users &

Obsolete Software

Inconsistent processing

Unreliable results or performance

Inadequate support of business needs

Incorrect or inadequate interfaces

with other systems

Inadequate performance and security

controls

Incorrect file handling

Srihari Techsoft
Objectives of testing
Objectives of testing

!"ecuting a program with the intent of

!"ecuting a program with the intent of
finding an
finding an
error
error
#
#

To chec$ if the system meets the

To chec$ if the system meets the
reuirements and be e"ecuted
reuirements and be e"ecuted
successfully in the Intended environment#
successfully in the Intended environment#

To chec$ if the system is % &it for purpose'#

To chec$ if the system is % &it for purpose'#

To chec$ if the system does what it is

To chec$ if the system does what it is
e"pected to do#
e"pected to do#

Srihari Techsoft
Objectives of testing
Objectives of testing

( good test case is one that has a

( good test case is one that has a
probability of finding an as yet
probability of finding an as yet
undiscovered error#
undiscovered error#

( successful test is one that uncovers a

( successful test is one that uncovers a
yet undiscovered error#
yet undiscovered error#

( good test is not redundant#

( good test is not redundant#

( good test should be %best of breed'#

( good test should be %best of breed'#

( good test should neither be too simple

( good test should neither be too simple
nor too comple"#
nor too comple"#

Srihari Techsoft
Objective of a Software Tester
Objective of a Software Tester

&ind bugs as early as possible and ma$e sure

&ind bugs as early as possible and ma$e sure
they get fi"ed#
they get fi"ed#

To understand the application well#

To understand the application well#

Study the functionality in detail to find where the

Study the functionality in detail to find where the
bugs are li$ely to occur#
bugs are li$ely to occur#

Study the code to ensure that each and every

Study the code to ensure that each and every
line of code is tested#
line of code is tested#

)reate test cases in such a way that testing is

)reate test cases in such a way that testing is
done to uncover the hidden bugs and also
done to uncover the hidden bugs and also
ensure that the software is usable and reliable
ensure that the software is usable and reliable

Srihari Techsoft
V!IFICATIO" & VA#I$ATIO"
V!IFICATIO" & VA#I$ATIO"


Verification
Verification
* typically involves reviews and meeting
* typically involves reviews and meeting
to evaluate documents+ plans+ code+ reuirements+
to evaluate documents+ plans+ code+ reuirements+
and specifications# This can be done with chec$lists+
and specifications# This can be done with chec$lists+
issues lists+ wal$throughs+ and inspection meeting#
issues lists+ wal$throughs+ and inspection meeting#
Validation
Validation
* typically involves actual testing and
* typically involves actual testing and
ta$es place after verifications are completed#
ta$es place after verifications are completed#


,alidation and ,erification process continue in
,alidation and ,erification process continue in
a cycle till the software becomes defects free#
a cycle till the software becomes defects free#

Srihari Techsoft
TSTA%I#IT&
TSTA%I#IT&

Operabilit'
Operabilit'

Observe(abilit'
Observe(abilit'

Controllabilit'
Controllabilit'

$ecomposabilit'
$ecomposabilit'

Stabilit'
Stabilit'

)nderstandabilit'
)nderstandabilit'

Srihari Techsoft
*lan
$o
C+ec,
Action
Software Development Process Cycle

Srihari Techsoft

PLAN (P):
PLAN (P):
Device a plan Define your ob!ective and
Device a plan Define your ob!ective and
determine the strategy
determine the strategy
and supporting methods
and supporting methods
required to achieve that ob!ective
required to achieve that ob!ective

DO (D):
DO (D):
"#ecute the plan Create the conditions
"#ecute the plan Create the conditions
and perform the necessary training to e#ecute the
and perform the necessary training to e#ecute the
plan
plan

CHECK (C):
CHECK (C):
Chec$ the results Chec$ to determine
Chec$ the results Chec$ to determine
whether wor$ is progressing according to the plan
whether wor$ is progressing according to the plan
and whether the results are obtained
and whether the results are obtained

ACTION (A):
ACTION (A):
%a$e the necessary and appropriate
%a$e the necessary and appropriate
action if chec$up reveals that the wor$ is not being
action if chec$up reveals that the wor$ is not being
performed according to plan or not as anticipated
performed according to plan or not as anticipated

Srihari Techsoft
QUALITY PRINCIPLES
QUALITY PRINCIPLES
Quality - the m!t im"#ta$t %a&t# a%%e&ti$' a$
Quality - the m!t im"#ta$t %a&t# a%%e&ti$' a$
#'a$i(ati$)! l$'-te#m "e#%#ma$&e*
#'a$i(ati$)! l$'-te#m "e#%#ma$&e*

Quality - the +ay t a&hie,e im"#,e-
Quality - the +ay t a&hie,e im"#,e-
"#-u&ti,ity a$- &m"etiti,e$e!! i$
"#-u&ti,ity a$- &m"etiti,e$e!! i$
a$y #'a$i(ati$*
a$y #'a$i(ati$*
Quality - !a,e!* It -e! $t &!t*
Quality - !a,e!* It -e! $t &!t*
Quality - i! the !luti$ t the "#.lem/ $t a
Quality - i! the !luti$ t the "#.lem/ $t a
"#.lem*
"#.lem*

Srihari Techsoft
C!t % Quality
P#e,e$ti$ C!t
&mount spent before the product is actually
built Cost incurred on establishing methods
and procedures' training wor$ers' acquiring
tools and planning for quality
A""#ai!al &!t
&mount spent after the product is built but
before it is shipped to the user Cost of
inspection' testing' and reviews

Srihari Techsoft
0ailu#e C!t

&mount spent to repair failures
Cost associated with defective products
that have been delivered to the user or
moved into production' costs involve
repairing products to ma$e them fit as per
requirement

Srihari Techsoft
-ualit' Assurance -ualit' Control
( planned and systematic
set of activities necessary to
provide adeuate confidence
that reuirements are
properly established and
products or services conform
to specified reuirements#
The process by which
product uality is compared
with applicable standards-
and the action ta$en when
non*conformance is
detected#
(n activity that establishes
and evaluates the processes
to produce the products#
(n activity which verifies if
the product meets pre*
defined standards#

Srihari Techsoft
-ualit' Assurance -ualit' Assurance -ualit' Control -ualit' Control
Helps establish processes# Helps establish processes# Implements the process# Implements the process#
Sets up measurements Sets up measurements
programs to evaluate programs to evaluate
processes# processes#
,erifies if specific ,erifies if specific
attributes are in a specific attributes are in a specific
product or Service product or Service
Identifies wea$nesses in Identifies wea$nesses in
processes and improves processes and improves
them# them#
Identifies defects for the Identifies defects for the
primary purpose of primary purpose of
correcting defects# correcting defects#

Srihari Techsoft
.( is the responsibility of .( is the responsibility of
the entire team# the entire team#
.) is the responsibility of the .) is the responsibility of the
tester# tester#
/revents the introduction of /revents the introduction of
issues or defects issues or defects
Detects+ reports and corrects Detects+ reports and corrects
defects defects
.( evaluates whether or not .( evaluates whether or not
uality control is wor$ing for uality control is wor$ing for
the primary purpose of the primary purpose of
determining whether or not determining whether or not
there is a wea$ness in the there is a wea$ness in the
process# process#
.) evaluates if the application .) evaluates if the application
is wor$ing for the primary is wor$ing for the primary
purpose of determining if there purpose of determining if there
is a flaw / defect in the is a flaw / defect in the
functionalities# functionalities#
Re!"$!i.ilitie! % QA a$- QC

Srihari Techsoft
.( improves the process .( improves the process
that is applied to multiple that is applied to multiple
products that will ever be products that will ever be
produced by a process# produced by a process#
.) improves the .) improves the
development of a specific development of a specific
product or service# product or service#
.( personnel should not .( personnel should not
perform uality control perform uality control
unless doing it to validate unless doing it to validate
uality control is wor$ing# uality control is wor$ing#
.) personnel may perform .) personnel may perform
uality assurance tas$s if uality assurance tas$s if
and when reuired# and when reuired#
Re!"$!i.ilitie! % QA a$- QC

Srihari Techsoft
SEI 1 C22
Software "ngineering Institute (SEI) developed Capability
*aturity *odel (C22)
C22 describes the prime elements + planning' engineering'
managing software development and maintenance
C22 can be used for
,
Software process improvement
,
Software process assessment
,
Software capability evaluations

Srihari Techsoft
The C22 i! #'a$i(e- i$t %i,e matu#ity le,el
I$itial
Le,el 3
Re"eata.le
Le,el 4
De%i$e-
Le,el 5
2a$a'e-
Le,el 6
O"timi(i$'
Le,el 7
Di!&i"li$e- P#&e!!
Sta$-a#- C$!i!te$&e
P#&e!!
P#e-i&ta.le P#&e!!
C$ti$uu!
Im"#,eme$t P#&e!!

Srihari Techsoft
Phases of SD-C
,
.equirement Specification and
&nalysis
,
Design
,
Coding
,
%esting
,
Implementation
,
*aintenance
SO0T8ARE DE9ELOP2ENT LI0E
CYCLE (SDLC)

Srihari Techsoft
0euirement Specification
and (nalysis
1ser 0euirement
Specification 21S03
Software 0euirement
Specification 2S0S3

Srihari Techsoft
%he output of S.S is the input of design phase
%wo types of design +
/igh -evel Design (/-D)
-ow -evel Design (--D)
De!i'$

Srihari Techsoft

-ist of modules and a brief description of each

module

0rief functionality of each module

Interface relationship among modules

Dependencies between modules (if & e#ists' 0

e#ists etc)

Database tables identified along with $ey

elements

Overall architecture diagrams along with

technology details
Hi'h Le,el De!i'$ (HLD)

Srihari Techsoft

Detailed functional logic of the module' in

pseudo code

Database tables' with all elements'

including their type and si1e

&ll interface details

&ll dependency issues

"rror message listings

Complete input and outputs for a module

L+ Le,el De!i'$ (LLD)

Srihari Techsoft
0rea$ing down the product into independent
modules to arrive at micro levels
2 different approaches followed in designing 3
%op Down &pproach
0ottom Up &pproach
The De!i'$ "#&e!!

Srihari Techsoft
T"--+$ a""#a&h

Srihari Techsoft
:ttm-U" A""#a&h

Srihari Techsoft
C-i$'
Developers use the --D document and
write the code in the programming language
specified
Te!ti$'
%he testing process involves development of
a test plan' e#ecuting the plan and
documenting the test results
Im"leme$tati$
Installation of the product in its operational
environment

Srihari Techsoft
2ai$te$a$&e
&fter the software is released and the client starts
using the software' maintenance phase is started
4 things happen + 0ug fi#ing' Upgrade' "nhancement
0ug fi#ing 3 bugs arrived due to some untested
scenarios
Upgrade 3 Upgrading the application to the newer
versions of the software
"nhancement + &dding some new features into the
e#isting software

Srihari Techsoft
SO0T8ARE LI0E CYCLE 2ODELS
8ATER0ALL 2ODEL
9-PROCESS 2ODEL
SPIRAL 2ODEL
PROTOTYPE 2ODEL
INCRE2ENTAL 2ODEL
E9OLUTIONARY DE9ELOP2ENT
2ODEL

P#;e&t 2a$a'eme$t
P#;e&t 2a$a'eme$t

Pro!ect Staffing
Pro!ect Staffing

Pro!ect Planning
Pro!ect Planning

Pro!ect Scheduling
Pro!ect Scheduling

Srihari Techsoft
P#;e&t Sta%%i$'
P#;e&t Sta%%i$'

Pro!ect budget may not allow to utili1e

Pro!ect budget may not allow to utili1e
highly 3 paid staff
highly 3 paid staff

Staff with the appropriate e#perience may not

Staff with the appropriate e#perience may not
be available
be available

Srihari Techsoft
P#;e&t Pla$$i$'
P#;e&t Pla$$i$'
Pla$ Pla$ De!&#i"ti$ De!&#i"ti$
Quality "la$ Quality "la$ Describes the quality procedures and Describes the quality procedures and
standards used in a pro!ect standards used in a pro!ect
9ali-ati$ "la$ 9ali-ati$ "la$ Describes the approach' resources and Describes the approach' resources and
schedule used for system validation schedule used for system validation
C$%i'u#ati$ C$%i'u#ati$
ma$a'eme$t "la$ ma$a'eme$t "la$
Describes the configuration management Describes the configuration management
procedures and structures to be used procedures and structures to be used
2ai$te$a$&e 2ai$te$a$&e
"la$ "la$
Predicts the maintenance requirements of the Predicts the maintenance requirements of the
system5 maintenance costs and efforts system5 maintenance costs and efforts
required required
Sta%% Sta%%
-e,el"me$t "la$ -e,el"me$t "la$
Describes how the s$ills and e#perience of Describes how the s$ills and e#perience of
the pro!ect team members will be developed the pro!ect team members will be developed

Srihari Techsoft
P#;e&t S&he-uli$'
P#;e&t S&he-uli$'

0ar charts and &ctivity 6etwor$s

0ar charts and &ctivity 6etwor$s

Scheduling problems
Scheduling problems

Srihari Techsoft
RISK 2ANA<E2ENT
RISK 2ANA<E2ENT

.is$ identification
.is$ identification

.is$ &nalysis
.is$ &nalysis

.is$ Planning
.is$ Planning

.is$ *onitoring
.is$ *onitoring

Srihari Techsoft


Ri!=
Ri!=
Ri!=
Ri!=
ty"e
ty"e
De!&#i"ti$
De!&#i"ti$
Staff Staff
turnover turnover
Pro!ect Pro!ect "#perienced staff will leave the "#perienced staff will leave the
pro!ect before it is finished pro!ect before it is finished
*anagement *anagement
change change
Pro!ect Pro!ect %here will be a change of %here will be a change of
organi1ational management with organi1ational management with
different priorities different priorities
/ardware /ardware
unavailability unavailability
Pro!ect Pro!ect /ardware which is essential for the /ardware which is essential for the
pro!ect will not be delivered on pro!ect will not be delivered on
schedule schedule
.equirements .equirements
change change
Pro!ect & Pro!ect &
Product Product
%here will be a larger number of %here will be a larger number of
changes to the requirements than changes to the requirements than
anticipated anticipated

Srihari Techsoft


Ri!=
Ri!=
Ri!=
Ri!=
ty"e
ty"e
De!&#i"ti$
De!&#i"ti$
Specification Specification
delays delays
Pro!ect & Pro!ect &
Product Product
Specifications of essential Specifications of essential
interfaces are not available on interfaces are not available on
schedule schedule
Si1e under Si1e under
estimate estimate
Pro!ect & Pro!ect &
Product Product
%he si1e of the system has been %he si1e of the system has been
under estimated under estimated
C&S" tool under C&S" tool under
performance performance
Product Product C&S" tools which support the C&S" tools which support the
pro!ect do not perform as pro!ect do not perform as
anticipated anticipated
%echnology %echnology
change change
0usiness 0usiness %he underlying technology on %he underlying technology on
which the system is built is which the system is built is
superseded by new technology superseded by new technology
Product Product
competition competition
0usiness 0usiness & competitive product is mar$eted & competitive product is mar$eted
before the system is completed before the system is completed

Srihari Techsoft
*C version
Initial s'stem
$C
version
VMS
version
)ni.
version
Mainframe
version
/or,station
version
C$%i'u#ati$ 2a$a'eme$t
Sun
version

Srihari Techsoft
C$%i'u#ati$ 2a$a'eme$t (C2)
Sta$-a#-!

C* should be based on a set of standards'

which are applied within an organi1ation

Srihari Techsoft
C2 Pla$$i$'

Documents' required for future system

maintenance' should be identified and included
as managed documents

It defines the types of documents to be

managed and a document naming scheme

Srihari Techsoft

Cha$'e 2a$a'eme$t

7eeping and managing the changes and

ensuring that they are implemented in the most
cost+effective way

Srihari Techsoft

Cha$'e Re>ue!t %#m
& part of the C* planning process

.ecords change required

Change suggested by

.eason why change was suggested

Urgency of change

.ecords change evaluation

Impact analysis

Change cost

.ecommendations(system maintenance staff)

Srihari Techsoft
9ERSION AND RELEASE 2ANA<E2ENT

Invent identification scheme for system

versions and plan when new system version is
to be produced

"nsure that version management procedures

and tools are properly applied and to plan and
distribute new system releases

Srihari Techsoft
9e#!i$!?9a#ia$t!?Relea!e!

9a#ia$t &n instance of a system which is

functionally identical but non 3 functionally
distinct from other instances of a system

9e#!i$! &n instance of a system' which is

functionally distinct in some way from other
system instances

Relea!e &n instance of a system' which is

distributed to users outside of the development
team

Srihari Techsoft

Srihari Techsoft
SO0T8ARE TESTIN< LI0ECYCLE -
PHASES
, .equirements study
, %est Case Design and
Development
, %est "#ecution
, %est Closure
, %est Process &nalysis

Srihari Techsoft
Re>ui#eme$t! !tu-y
Re>ui#eme$t! !tu-y

%esting Cycle starts with the study of client8s

%esting Cycle starts with the study of client8s
requirements
requirements

Understanding of the requirements is very

Understanding of the requirements is very
essential for testing the product
essential for testing the product

Srihari Techsoft
A$aly!i! @ Pla$$i$'
A$aly!i! @ Pla$$i$'
,
%est ob!ective and coverage
%est ob!ective and coverage
,
Overall schedule
Overall schedule
,
Standards and *ethodologies
Standards and *ethodologies
,
.esources required' including necessary
.esources required' including necessary
training
training
,
.oles and responsibilities of the team
.oles and responsibilities of the team
members
members
,
%ools used
%ools used

Srihari Techsoft
Te!t Ca!e De!i'$ a$- De,el"me$t
Te!t Ca!e De!i'$ a$- De,el"me$t
,
Component Identification
Component Identification
,
%est Specification Design
%est Specification Design
,
%est Specification .eview
%est Specification .eview
Te!t EAe&uti$
Te!t EAe&uti$
,
Code .eview
Code .eview
,
%est e#ecution and evaluation
%est e#ecution and evaluation
,
Performance and simulation
Performance and simulation

Srihari Techsoft
Te!t Cl!u#e
Te!t Cl!u#e
,
%est summary report
%est summary report
,
Pro!ect De+brief
Pro!ect De+brief
,
Pro!ect Documentation
Pro!ect Documentation
Te!t P#&e!! A$aly!i!
Te!t P#&e!! A$aly!i!
&nalysis done on the reports and improving
&nalysis done on the reports and improving
the application8s performance by implementing
the application8s performance by implementing
new technology and additional features
new technology and additional features

Srihari Techsoft

Srihari Techsoft
Te!ti$' Le,el!
,
Unit testing
Unit testing
,
Integration testing
Integration testing
,
System testing
System testing
,
&cceptance testing
&cceptance testing

Srihari Techsoft
U$it te!ti$'
U$it te!ti$'

%he most 9micro8 scale of testing

%he most 9micro8 scale of testing

%ests done on particular functions or code

%ests done on particular functions or code
modules
modules

.equires $nowledge of the internal program

.equires $nowledge of the internal program
design and code
design and code

Done by Programmers (not by testers)

Done by Programmers (not by testers)


Srihari Techsoft
U$it te!ti$'
O.;e&ti,e!
O.;e&ti,e!

%o test the function of a program or unit of
%o test the function of a program or unit of
code such as a program or module
code such as a program or module

%o test internal logic

%o test internal logic

%o verify internal design

%o verify internal design

%o test path & conditions coverage

%o test path & conditions coverage

%o test e#ception conditions & error

%o test e#ception conditions & error
handling
handling
8he$
8he$

&fter modules are coded
&fter modules are coded
I$"ut
I$"ut

Internal &pplication Design
Internal &pplication Design

*aster %est Plan

*aster %est Plan

Unit %est Plan

Unit %est Plan
Out"ut
Out"ut

Unit %est .eport
Unit %est .eport

Srihari Techsoft
8h
8h

Developer
Developer
2eth-!
2eth-!

:hite 0o# testing techniques
:hite 0o# testing techniques

%est Coverage techniques

%est Coverage techniques
Tl!
Tl!

Debug
Debug

.e+structure
.e+structure

Code &naly1ers
Code &naly1ers

Path5statement coverage tools

Path5statement coverage tools
E-u&ati$
E-u&ati$

%esting *ethodology
%esting *ethodology

"ffective use of tools

"ffective use of tools

Srihari Techsoft
I$&#eme$tal i$te'#ati$ te!ti$'
I$&#eme$tal i$te'#ati$ te!ti$'

Continuous testing of an application as and

Continuous testing of an application as and
when a new functionality is added
when a new functionality is added

&pplication8s functionality aspects are required

&pplication8s functionality aspects are required
to be independent enough to wor$ separately
to be independent enough to wor$ separately
before completion of development
before completion of development

Done by programmers or testers

Done by programmers or testers

Srihari Techsoft
I$te'#ati$ Te!ti$'
I$te'#ati$ Te!ti$'

%esting of combined parts of an application to

%esting of combined parts of an application to
determine their functional correctness
determine their functional correctness

9
9
Parts8 can be
Parts8 can be
,
code modules
code modules
,
individual applications
individual applications
,
client5server applications on a networ$
client5server applications on a networ$

Srihari Techsoft
Ty"e! % I$te'#ati$ Te!ti$'
Ty"e! % I$te'#ati$ Te!ti$'
,
0ig 0ang testing
0ig 0ang testing
,
%op Down Integration testing
%op Down Integration testing
,
0ottom Up Integration testing
0ottom Up Integration testing

Srihari Techsoft
I$te'#ati$ te!ti$'
O.;e&ti,e!
O.;e&ti,e!

%o technically verify proper
%o technically verify proper
interfacing between modules' and
interfacing between modules' and
within sub+systems
within sub+systems
8he$
8he$

&fter modules are unit tested
&fter modules are unit tested
I$"ut
I$"ut

Internal & "#ternal &pplication
Internal & "#ternal &pplication
Design
Design

*aster %est Plan

*aster %est Plan

Integration %est Plan

Integration %est Plan
Out"ut
Out"ut

Integration %est report
Integration %est report

Srihari Techsoft
8h
8h

Developers
Developers
2eth-!
2eth-!

:hite and 0lac$ 0o#
:hite and 0lac$ 0o#
techniques
techniques

Problem 5
Problem 5
Configuration
Configuration
*anagement
*anagement
Tl!
Tl!

Debug
Debug

.e+structure
.e+structure

Code &naly1ers
Code &naly1ers
E-u&ati$
E-u&ati$

%esting *ethodology
%esting *ethodology

"ffective use of tools

"ffective use of tools

Srihari Techsoft
Sy!tem Te!ti$'
Sy!tem Te!ti$'

O.;e&ti,e!
O.;e&ti,e!

%o verify that the system components perform %o verify that the system components perform
control functions control functions

%o perform inter+system test %o perform inter+system test

%o demonstrate that the system performs both %o demonstrate that the system performs both
functionally and operationally as specified functionally and operationally as specified

%o perform appropriate types of tests relating %o perform appropriate types of tests relating
to %ransaction ;low' Installation' .eliability' to %ransaction ;low' Installation' .eliability'
.egression etc .egression etc
8he$
8he$

&fter Integration %esting &fter Integration %esting
I$"ut
I$"ut

Detailed .equirements & "#ternal &pplication Detailed .equirements & "#ternal &pplication
Design Design

*aster %est Plan *aster %est Plan

System %est Plan System %est Plan

Out"ut
Out"ut

System %est .eport System %est .eport

Srihari Techsoft
8h
8h

Development %eam and Users
Development %eam and Users
2eth-!
2eth-!

Problem 5 Configuration
Problem 5 Configuration
*anagement
*anagement
Tl!
Tl!

.ecommended set of tools
.ecommended set of tools
E-u&ati$
E-u&ati$

%esting *ethodology
%esting *ethodology

"ffective use of tools

"ffective use of tools

Srihari Techsoft
Sy!tem! I$te'#ati$ Te!ti$'
O.;e&ti,e!
O.;e&ti,e!

%o test the co+e#istence of products and %o test the co+e#istence of products and
applications that are required to perform applications that are required to perform
together in the production+li$e operational together in the production+li$e operational
environment (hardware' software' networ$) environment (hardware' software' networ$)

%o ensure that the system functions together %o ensure that the system functions together
with all the components of its environment as a with all the components of its environment as a
total system total system

%o ensure that the system releases can be %o ensure that the system releases can be
deployed in the current environment deployed in the current environment
8he$
8he$

&fter system testing &fter system testing

Often performed outside of pro!ect life+cycle Often performed outside of pro!ect life+cycle
I$"ut
I$"ut

%est Strategy %est Strategy

*aster %est Plan *aster %est Plan

Systems Integration %est Plan Systems Integration %est Plan

Out"ut
Out"ut

Systems Integration %est report Systems Integration %est report

Srihari Techsoft
8h
8h

System %esters
System %esters
2eth-!
2eth-!

:hite and 0lac$ 0o# techniques
:hite and 0lac$ 0o# techniques

Problem 5 Configuration
Problem 5 Configuration
*anagement
*anagement
Tl!
Tl!

.ecommended set of tools
.ecommended set of tools
E-u&ati$
E-u&ati$

%esting *ethodology
%esting *ethodology

"ffective use of tools

"ffective use of tools

Srihari Techsoft
A&&e"ta$&e Te!ti$'
O.;e&ti,e!
O.;e&ti,e!

%o verify that the system meets
%o verify that the system meets
the user requirements
the user requirements
8he$
8he$

&fter System %esting
&fter System %esting
I$"ut
I$"ut

0usiness 6eeds & Detailed
0usiness 6eeds & Detailed
.equirements
.equirements

*aster %est Plan

*aster %est Plan

User &cceptance %est Plan

User &cceptance %est Plan
Out"ut
Out"ut

User &cceptance %est report
User &cceptance %est report

Srihari Techsoft
8h
8h
Users 5 "nd Users
Users 5 "nd Users
2eth-!
2eth-!

0lac$ 0o# techniques
0lac$ 0o# techniques

Problem 5 Configuration
Problem 5 Configuration
*anagement
*anagement
Tl!
Tl!
Compare' $eystro$e capture & playbac$'
Compare' $eystro$e capture & playbac$'
regression testing
regression testing
E-u&ati$
E-u&ati$

%esting *ethodology
%esting *ethodology

"ffective use of tools

"ffective use of tools

Product $nowledge
Product $nowledge

0usiness .elease Strategy

0usiness .elease Strategy

Srihari Techsoft
TESTIN< 2ETHODOLO<IES
TESTIN< 2ETHODOLO<IES
AND TYPES
AND TYPES

Te!ti$' meth-l'ie!
Te!ti$' meth-l'ie!
0lac$ bo# testing
0lac$ bo# testing
:hite bo# testing
:hite bo# testing
Incremental testing
Incremental testing
%hread testing
%hread testing

Srihari Techsoft

:la&= .A te!ti$'
:la&= .A te!ti$'
,
6o $nowledge of internal design or code
6o $nowledge of internal design or code
required
required
,
%ests are based on requirements and
%ests are based on requirements and
functionality
functionality

8hite .A te!ti$'
8hite .A te!ti$'
,
7nowledge of the internal program design
7nowledge of the internal program design
and code required
and code required
,
%ests are based on coverage of code
%ests are based on coverage of code
statements'branches'paths'conditions
statements'branches'paths'conditions

Srihari Techsoft

Incorrect or missing functions

Incorrect or missing functions

Interface errors
Interface errors

"rrors in data structures or e#ternal database

"rrors in data structures or e#ternal database
access
access

Performance errors
Performance errors

Initiali1ation and termination errors

Initiali1ation and termination errors
:la&= :A - te!ti$' te&h$i>ue
:la&= :A - te!ti$' te&h$i>ue

Srihari Techsoft
:la&= .A ? 0u$&ti$al te!ti$'
:la&= .A ? 0u$&ti$al te!ti$'

0ased on requirements and functionality

0ased on requirements and functionality

6ot based on any $nowledge of internal

6ot based on any $nowledge of internal
design or code
design or code

Covers all combined parts of a system

Covers all combined parts of a system

%ests are data driven

%ests are data driven

Srihari Techsoft
8hite .A te!ti$' ? St#u&tu#al te!ti$'
8hite .A te!ti$' ? St#u&tu#al te!ti$'

0ased on $nowledge of internal logic of an

0ased on $nowledge of internal logic of an
application<s code
application<s code

0ased on coverage of code statements'

0ased on coverage of code statements'
branches' paths' conditions
branches' paths' conditions

%ests are logic driven

%ests are logic driven

Srihari Techsoft
0u$&ti$al te!ti$'
0u$&ti$al te!ti$'

0lac$ bo# type testing geared to functional

0lac$ bo# type testing geared to functional


requirements of an application
requirements of an application

Done by testers
Done by testers
Sy!tem te!ti$'
Sy!tem te!ti$'

0lac$ bo# type testing that is based on overall

0lac$ bo# type testing that is based on overall
requirements specifications= covering all combined
requirements specifications= covering all combined
parts of the system
parts of the system
E$--t-e$- te!ti$'
E$--t-e$- te!ti$'

Similar to system testing= involves testing of a

Similar to system testing= involves testing of a
complete application environment in a situation that
complete application environment in a situation that
mimics real+world use
mimics real+world use

Srihari Techsoft
Sa$ity te!ti$'
Sa$ity te!ti$'

Initial effort to determine if a new software

Initial effort to determine if a new software
version is performing well enough to accept
version is performing well enough to accept
it for a ma!or testing effort
it for a ma!or testing effort
Re'#e!!i$ te!ti$'
Re'#e!!i$ te!ti$'

.e+testing after fi#es or modifications of the

.e+testing after fi#es or modifications of the
software or its environment
software or its environment

Srihari Techsoft
A&&e"ta$&e te!ti$'
A&&e"ta$&e te!ti$'

;inal testing based on specifications of the

;inal testing based on specifications of the
end+user or customer
end+user or customer
La- te!ti$'
La- te!ti$'

%esting an application under heavy loads

%esting an application under heavy loads

"g %esting of a web site under a range of

"g %esting of a web site under a range of
loads to determine' when the system
loads to determine' when the system
response time degraded or fails
response time degraded or fails

Srihari Techsoft
St#e!! Te!ti$'
St#e!! Te!ti$'

%esting under unusually heavy loads' heavy

%esting under unusually heavy loads' heavy


repetition of certain actions or inputs' input of
repetition of certain actions or inputs' input of
large numerical values' large comple# queries
large numerical values' large comple# queries
to a database etc
to a database etc

%erm often used interchangeably with 9load8

%erm often used interchangeably with 9load8
and 9performance8 testing
and 9performance8 testing
Pe#%#ma$&e te!ti$'
Pe#%#ma$&e te!ti$'

%esting how well an application complies to

%esting how well an application complies to
performance requirements
performance requirements

Srihari Techsoft
I$!tall?u$i$!tall te!ti$'
I$!tall?u$i$!tall te!ti$'

%esting of full'partial or upgrade

%esting of full'partial or upgrade
install5uninstall process
install5uninstall process
Re&,e#y te!ti$'
Re&,e#y te!ti$'

%esting how well a system recovers from

%esting how well a system recovers from
crashes' /: failures or other problems
crashes' /: failures or other problems
Cm"ati.ility te!ti$'
Cm"ati.ility te!ti$'

%esting how well software performs in a

%esting how well software performs in a
particular /:5S:5OS56: environment
particular /:5S:5OS56: environment

Srihari Techsoft
EA"l#at#y te!ti$' ? a--h& te!ti$'
EA"l#at#y te!ti$' ? a--h& te!ti$'

Informal S: test that is not based on formal test

Informal S: test that is not based on formal test
plans or test cases= testers will be learning the
plans or test cases= testers will be learning the
S: in totality as they test it
S: in totality as they test it
Cm"a#i!$ te!ti$'
Cm"a#i!$ te!ti$'

Comparing S: strengths and wea$ness to

Comparing S: strengths and wea$ness to
competing products
competing products

Srihari Techsoft
Al"ha te!ti$'
,
%esting done when development is nearing
completion= minor design changes may still
be made as a result of such testing

:eta-te!ti$'
,
%esting when development and testing are
essentially completed and final bugs and
problems need to be found before release

Srihari Techsoft
2utati$ te!ti$'
2utati$ te!ti$'

%o determining if a set of test data or test cases is

%o determining if a set of test data or test cases is
useful' by deliberately introducing various bugs
useful' by deliberately introducing various bugs

.e+testing with the original test data5cases to

.e+testing with the original test data5cases to
determine if the bugs are detected
determine if the bugs are detected

Srihari Techsoft

Srihari Techsoft
8hite :A - te!ti$' te&h$i>ue
8hite :A - te!ti$' te&h$i>ue

&ll independent paths within a module have been

&ll independent paths within a module have been
e#ercised at least once
e#ercised at least once

"#ercise all logical decisions on their

"#ercise all logical decisions on their
true
true
and
and
false
false

sides
sides

"#ecute all loops at their boundaries and within their

"#ecute all loops at their boundaries and within their
operational bounds
operational bounds

"#ercise internal data structures to ensure their

"#ercise internal data structures to ensure their
validity
validity

Srihari Techsoft
%his white bo# technique focuses on the validity
%his white bo# technique focuses on the validity
of loop constructs
of loop constructs
> different classes of loops can be defined
> different classes of loops can be defined
,
simple loops
simple loops
,
nested loops
nested loops
,
concatenated loops
concatenated loops
,
Unstructured loops
Unstructured loops
L" Te!ti$'

Srihari Techsoft
Othe# 8hite :A Te&h$i>ue!
Othe# 8hite :A Te&h$i>ue!

Stateme$t C,e#a'e Stateme$t C,e#a'e 3 e#ecute all statements at least once 3 e#ecute all statements at least once
De&i!i$ C,e#a'e De&i!i$ C,e#a'e 3 e#ecute each decision direction at least 3 e#ecute each decision direction at least
once once
C$-iti$ C,e#a'e C$-iti$ C,e#a'e 3 e#ecute each decision with all possible 3 e#ecute each decision with all possible
outcomes at least once outcomes at least once
De&i!i$ ? C$-iti$ De&i!i$ ? C$-iti$ &,e#a'e &,e#a'e 3 e#ecute all possible 3 e#ecute all possible
combinations of condition outcomes in combinations of condition outcomes in
each decision each decision
2ulti"le &$-iti$ C,e#a'e 2ulti"le &$-iti$ C,e#a'e 3 Invo$es each point of entry at 3 Invo$es each point of entry at
least once least once
!"amples 44 !"amples 44

Srihari Techsoft
Stateme$t C,e#a'e 1 EAam"le!
Stateme$t C,e#a'e 1 EAam"le!
!g# ( 5 6
!g# ( 5 6
If 2( 7 83 Then
If 2( 7 83 Then


6 7 9 5 :
6 7 9 5 :
!nd*If
!nd*If
While 2( ; <3 Do
While 2( ; <3 Do
0ead 293
0ead 293
( 7 ( * =
( 7 ( * =
!nd*While*Do
!nd*While*Do

Srihari Techsoft
De&i!i$ C,e#a'e - EAam"le
De&i!i$ C,e#a'e - EAam"le
If & ? @A or & B 2A %hen If & ? @A or & B 2A %hen
0 C D E F 0 C D E F
C$-iti$ C,e#a'e 1 EAam"le
C$-iti$ C,e#a'e 1 EAam"le
& C D & C D
If (& B 4) or (& ? 0) %hen If (& B 4) or (& ? 0) %hen
0 C D E F 0 C D E F
"nd+If+%hen "nd+If+%hen
:hile (& B A) and (6ot "O;) Do :hile (& B A) and (6ot "O;) Do
.ead (D) .ead (D)
& C & + @ & C & + @
"nd+:hile+Do "nd+:hile+Do

Srihari Techsoft
I$&#eme$tal Te!ti$'
I$&#eme$tal Te!ti$'

& disciplined method of testing the interfaces

& disciplined method of testing the interfaces
between unit+tested programs as well as
between unit+tested programs as well as
between system components
between system components

Involves adding unit+testing program module

Involves adding unit+testing program module
or component one by one' and testing each
or component one by one' and testing each
result and combination
result and combination


Srihari Techsoft
The#e a#e t+ ty"e! % i$&#eme$tal te!ti$'
The#e a#e t+ ty"e! % i$&#eme$tal te!ti$'

T"--+$
T"--+$
3 testing form the top of the
3 testing form the top of the
module hierarchy and wor$ down to the bottom
module hierarchy and wor$ down to the bottom
*odules are added in descending hierarchical
*odules are added in descending hierarchical
order
order

:ttm-u"
:ttm-u"
3 testing from the bottom of the
3 testing from the bottom of the
hierarchy and wor$s up to the top *odules are
hierarchy and wor$s up to the top *odules are
added in ascending hierarchical order
added in ascending hierarchical order

Srihari Techsoft
Te!ti$' Le,el!?
Te!ti$' Le,el!?
Te&h$i>ue!
Te&h$i>ue!
8hite
8hite
:A
:A
:la&=
:la&=
:A
:A
I$&#e-
I$&#e-
me$tal
me$tal
Th#ea-
Th#ea-
U$it Te!ti$'
U$it Te!ti$' B B
I$te'#ati$
I$te'#ati$
Te!ti$'
Te!ti$'
B B B B
B B
Sy!tem Te!ti$'
Sy!tem Te!ti$' B B
A&&e"ta$&e
A&&e"ta$&e
Te!ti$'
Te!ti$'
B B

2a;# Te!ti$' Ty"e!
2a;# Te!ti$' Ty"e!

Stress 5 -oad %esting

Performance %esting

.ecovery %esting

Conversion %esting

Usability %esting

Configuration %esting

Srihari Techsoft
St#e!! ? La- Te!t
St#e!! ? La- Te!t

"valuates a system or component at or beyond

"valuates a system or component at or beyond
the limits of its specified requirements
the limits of its specified requirements

Determines the load under which it fails and

Determines the load under which it fails and


how
how

Srihari Techsoft
Pe#%#ma$&e Te!t
Pe#%#ma$&e Te!t

"valuate the compliance of a system or

"valuate the compliance of a system or
component with specified performance
component with specified performance
requirements
requirements

Often performed using an automated test tool

Often performed using an automated test tool
to simulate large number of users
to simulate large number of users

Srihari Techsoft
Re&,e#y Te!t
Re&,e#y Te!t
Confirms that the system recovers from
Confirms that the system recovers from
e#pected or une#pected events without loss
e#pected or une#pected events without loss
of data or functionality
of data or functionality
"g
"g

Shortage of dis$ space

Shortage of dis$ space

Une#pected loss of communication

Une#pected loss of communication

Power out conditions

Power out conditions

Srihari Techsoft
C$,e#!i$ Te!t
C$,e#!i$ Te!t

%esting of code that is used to convert data

%esting of code that is used to convert data
from e#isting systems for use in the newly
from e#isting systems for use in the newly
replaced systems
replaced systems

Srihari Techsoft
U!a.ility Te!t
U!a.ility Te!t

%esting the system for the users

%esting the system for the users
to learn and use the product
to learn and use the product

Srihari Techsoft
C$%i'u#ati$ Te!t
C$%i'u#ati$ Te!t

"#amines an application<s requirements for pre+

"#amines an application<s requirements for pre+
e#isting software' initial states and
e#isting software' initial states and
configuration in order to maintain proper
configuration in order to maintain proper
functionality
functionality

Srihari Techsoft
SO0T8ARE TESTIN< LI0ECYCLE -
PHASES
, .equirements study
, %est Case Design and
Development
, %est "#ecution
, %est Closure
, %est Process &nalysis

Srihari Techsoft
Re>ui#eme$t! !tu-y
Re>ui#eme$t! !tu-y

%esting Cycle starts with the study of client8s

%esting Cycle starts with the study of client8s
requirements
requirements

Understanding of the requirements is very

Understanding of the requirements is very
essential for testing the product
essential for testing the product

Srihari Techsoft
A$aly!i! @ Pla$$i$'
A$aly!i! @ Pla$$i$'
,
%est ob!ective and coverage
%est ob!ective and coverage
,
Overall schedule
Overall schedule
,
Standards and *ethodologies
Standards and *ethodologies
,
.esources required' including necessary
.esources required' including necessary
training
training
,
.oles and responsibilities of the team
.oles and responsibilities of the team
members
members
,
%ools used
%ools used

Srihari Techsoft
Te!t Ca!e De!i'$ a$- De,el"me$t
Te!t Ca!e De!i'$ a$- De,el"me$t
,
Component Identification
Component Identification
,
%est Specification Design
%est Specification Design
,
%est Specification .eview
%est Specification .eview
Te!t EAe&uti$
Te!t EAe&uti$
,
Code .eview
Code .eview
,
%est e#ecution and evaluation
%est e#ecution and evaluation
,
Performance and simulation
Performance and simulation

Srihari Techsoft
Te!t Cl!u#e
Te!t Cl!u#e
,
%est summary report
%est summary report
,
Pro!ect Documentation
Pro!ect Documentation
Te!t P#&e!! A$aly!i!
Te!t P#&e!! A$aly!i!
&nalysis done on the reports and improving
&nalysis done on the reports and improving
the application8s performance by implementing
the application8s performance by implementing
new technology and additional features
new technology and additional features

Srihari Techsoft
TEST PLAN
TEST PLAN

O.;e&ti,e!
O.;e&ti,e!

%o create a set of testing tas$s

%o create a set of testing tas$s

&ssign resources to each testing tas$

&ssign resources to each testing tas$

"stimate completion time for each testing tas$

"stimate completion time for each testing tas$

Document testing standards

Document testing standards

& document that describes the

& document that describes the

scope
scope

approach
approach

resources
resources

schedule
schedule
G
G
of intended test activities
of intended test activities

Identifies the
Identifies the

test items
test items

features to be tested
features to be tested

testing tas$s
testing tas$s

tas$ allotment
tas$ allotment

ris$s requiring contingency planning

ris$s requiring contingency planning

Srihari Techsoft
Pu#"!e % "#e"a#i$' a Te!t Pla$
Pu#"!e % "#e"a#i$' a Te!t Pla$

Halidate the acceptability of a software product

Halidate the acceptability of a software product

/elp the people outside the test group to understand

/elp the people outside the test group to understand
9why8 and 9how8 of product validation
9why8 and 9how8 of product validation

& %est Plan should be

& %est Plan should be

thorough enough (Overall coverage of test to be

thorough enough (Overall coverage of test to be
conducted)
conducted)

useful and understandable by the people inside and

useful and understandable by the people inside and
outside the test group
outside the test group

Srihari Techsoft
S&"e
S&"e

%he areas to be tested by the I& team

%he areas to be tested by the I& team

Specify the areas which are out of scope (screens'

Specify the areas which are out of scope (screens'


database' mainframe processes etc)
database' mainframe processes etc)
Te!t A""#a&h
Te!t A""#a&h

Details on how the testing is to be performed

Details on how the testing is to be performed

&ny specific strategy is to be followed for

&ny specific strategy is to be followed for


testing (including configuration management)
testing (including configuration management)

Srihari Techsoft
E$t#y C#ite#ia
E$t#y C#ite#ia
Harious steps to be performed before the start of a
Harious steps to be performed before the start of a
test ie Pre+requisites
test ie Pre+requisites
"g
"g

%imely environment set up

%imely environment set up

Starting the web server5app server

Starting the web server5app server

Successful implementation of the latest build etc

Successful implementation of the latest build etc
Re!u#&e!
Re!u#&e!
-ist of the people involved in the pro!ect and their
-ist of the people involved in the pro!ect and their
designation etc
designation etc

Srihari Techsoft
Ta!=!?Re!"$!i.ilitie!
%as$s to be performed and responsibilities
assigned to the various team members
EAit C#ite#ia
Contains tas$s li$e
,
0ringing down the system 5 server
,
.estoring system to pre+test environment
,
Database refresh etc
S&he-ule ? 2ile!t$e!
Deals with the final delivery date and the
various milestones dates

Srihari Techsoft
Ha#-+a#e ? S%t+a#e Re>ui#eme$t!
Ha#-+a#e ? S%t+a#e Re>ui#eme$t!

Details of PC8s 5 servers required to install the

Details of PC8s 5 servers required to install the


application or perform the testing
application or perform the testing

Specific software to get the application

Specific software to get the application


running or to connect to the database etc
running or to connect to the database etc
Ri!=! @ 2iti'ati$ Pla$!
Ri!=! @ 2iti'ati$ Pla$!

-ist out the possible ris$s during testing

-ist out the possible ris$s during testing

*itigation plans to implement incase the ris$

*itigation plans to implement incase the ris$


actually turns into a reality
actually turns into a reality

Srihari Techsoft
Tl! t .e u!e-
Tl! t .e u!e-

-ist the testing tools or utilities

-ist the testing tools or utilities

"g:in.unner' -oad.unner' %est Director'

"g:in.unner' -oad.unner' %est Director'
.ational .obot' I%P
.ational .obot' I%P
Deli,e#a.le!
Deli,e#a.le!

Harious deliverables due to the client at various

Harious deliverables due to the client at various


points of time ie Daily 5 wee$ly 5 start of the
points of time ie Daily 5 wee$ly 5 start of the


pro!ect end of the pro!ect etc
pro!ect end of the pro!ect etc

%hese include test plans' test procedures' test

%hese include test plans' test procedures' test


metric' status reports' test scripts etc
metric' status reports' test scripts etc

Srihari Techsoft
Re%e#e$&e!
Re%e#e$&e!

Procedures
Procedures

%emplates (Client specific or otherwise)

%emplates (Client specific or otherwise)

Standards 5 Juidelines eg Iview

Standards 5 Juidelines eg Iview

Pro!ect related documents (.SD' &DD'

Pro!ect related documents (.SD' &DD'
;SD etc)
;SD etc)

Srihari Techsoft
A$$eAu#e
A$$eAu#e

-in$s to documents which have been 5 will be

-in$s to documents which have been 5 will be
used in the course of testing
used in the course of testing
"g %emplates used for reports' test cases etc
"g %emplates used for reports' test cases etc

.eferenced documents can also be attached here

.eferenced documents can also be attached here
Si'$-%%
Si'$-%%

*utual agreement between the client and the I&

*utual agreement between the client and the I&
%eam
%eam

0oth leads5managers signing their agreement on

0oth leads5managers signing their agreement on
the %est Plan
the %est Plan

Srihari Techsoft
<- Te!t Pla$!
<- Te!t Pla$!

Developed and .eviewed early

Developed and .eviewed early

Clear' Complete and Specific

Clear' Complete and Specific

Specifies tangible deliverables that can be

Specifies tangible deliverables that can be
inspected
inspected

Staff $nows what to e#pect and when to e#pect it

Staff $nows what to e#pect and when to e#pect it

Srihari Techsoft
<- Te!t Pla$!
<- Te!t Pla$!

.ealistic quality levels for goals

.ealistic quality levels for goals

Includes time for planning

Includes time for planning

Can be monitored and updated

Can be monitored and updated

Includes user responsibilities

Includes user responsibilities

0ased on past e#perience

0ased on past e#perience

.ecogni1es learning curves

.ecogni1es learning curves

Srihari Techsoft
TEST CASES
TEST CASES

Te!t &a!e
Te!t &a!e
is defined as
is defined as

& set of test inputs' e#ecution conditions and

& set of test inputs' e#ecution conditions and
e#pected results' developed for a particular
e#pected results' developed for a particular
ob!ective
ob!ective

Documentation specifying inputs' predicted

Documentation specifying inputs' predicted
results and a set of e#ecution conditions for a test
results and a set of e#ecution conditions for a test
item
item

Srihari Techsoft

Specific inputs that will be tried and the

Specific inputs that will be tried and the
procedures that will be followed when the
procedures that will be followed when the
software tested
software tested

Sequence of one or more subtests e#ecuted as

Sequence of one or more subtests e#ecuted as
a sequence as the outcome and5or final state of
a sequence as the outcome and5or final state of
one subtests is the input and5or initial state of
one subtests is the input and5or initial state of
the ne#t
the ne#t

Specifies the pretest state of the &U% and its

Specifies the pretest state of the &U% and its
environment' the test inputs or conditions
environment' the test inputs or conditions

%he e#pected result specifies what the &U%

%he e#pected result specifies what the &U%
should produce from the test inputs
should produce from the test inputs

Srihari Techsoft
<- Te!t Pla$!
<- Te!t Pla$!

Developed and .eviewed early

Developed and .eviewed early

Clear' Complete and Specific

Clear' Complete and Specific

Specifies tangible deliverables that can be

Specifies tangible deliverables that can be
inspected
inspected

Staff $nows what to e#pect and when to e#pect it

Staff $nows what to e#pect and when to e#pect it

Srihari Techsoft
<- Te!t Pla$!
<- Te!t Pla$!

.ealistic quality levels for goals

.ealistic quality levels for goals

Includes time for planning

Includes time for planning

Can be monitored and updated

Can be monitored and updated

Includes user responsibilities

Includes user responsibilities

0ased on past e#perience

0ased on past e#perience

.ecogni1es learning curves

.ecogni1es learning curves

Srihari Techsoft
Te!t Ca!e!
Te!t Ca!e!
C$te$t!
C$te$t!

%est plan reference id

%est plan reference id

%est case
%est case

%est condition
%est condition

"#pected behavior
"#pected behavior

Srihari Techsoft
<- Te!t Ca!e!
<- Te!t Ca!e!
0i$- De%e&t!
0i$- De%e&t!

/ave high probability of finding a new defect

/ave high probability of finding a new defect

Unambiguous tangible result that can be

Unambiguous tangible result that can be
inspected
inspected

.epeatable and predictable

.epeatable and predictable

Srihari Techsoft
<- Te!t Ca!e!
<- Te!t Ca!e!

%raceable to requirements or design documents

%raceable to requirements or design documents

Push systems to its limits

Push systems to its limits

"#ecution and trac$ing can be automated

"#ecution and trac$ing can be automated

Do not mislead
Do not mislead

;easible
;easible

De%e&t Li%e Cy&le
De%e&t Li%e Cy&le
8hat i! De%e&tC
& defect is a variance from a desired
product attribute
T+ &ate'#ie! % -e%e&t! a#e
,
Hariance from product specifications
,
Hariance from Customer5User
e#pectations

Srihari Techsoft
9a#ia$&e %#m "#-u&t !"e&i%i&ati$
9a#ia$&e %#m "#-u&t !"e&i%i&ati$

Product built varies from the product specified

Product built varies from the product specified
9a#ia$&e %#m Cu!tme#?U!e# !"e&i%i&ati$
9a#ia$&e %#m Cu!tme#?U!e# !"e&i%i&ati$

& specification by the user not in the built

& specification by the user not in the built
product' but something not specified has been
product' but something not specified has been
included
included

Srihari Techsoft
De%e&t &ate'#ie!
8#$'
%he specifications have been implemented
incorrectly
2i!!i$'
& specified requirement is not in the built
product
EAt#a
& requirement incorporated into the product
that was not specified

Srihari Techsoft
De%e&t L'
De%e&t L'
,
Defect ID number
Defect ID number
,
Descriptive defect name and type
Descriptive defect name and type
,
Source of defect 3 test case or other source
Source of defect 3 test case or other source
,
Defect severity
Defect severity
,
Defect Priority
Defect Priority
,
Defect status (eg 6ew' open' fi#ed' closed'
Defect status (eg 6ew' open' fi#ed' closed'
reopen' re!ect)
reopen' re!ect)

Srihari Techsoft
K K
Date and time trac$ing for either the most
Date and time trac$ing for either the most
recent status change' or for each change in the
recent status change' or for each change in the
status
status
L L
Detailed description' including the steps
Detailed description' including the steps
necessary to reproduce the defect
necessary to reproduce the defect
M M
Component or program where defect was found
Component or program where defect was found
@A @A
Screen prints' logs' etc that will aid the
Screen prints' logs' etc that will aid the
developer in resolution process
developer in resolution process
@@ @@
Stage of origination
Stage of origination
@2 @2
Person assigned to research and5or corrects the
Person assigned to research and5or corrects the
defect
defect


Srihari Techsoft


Se,e#ity 9! P#i#ity
Se,e#ity 9! P#i#ity
Se,e#ity
Se,e#ity
;actor that shows how bad the defect is
;actor that shows how bad the defect is
and the impact it has on the product
and the impact it has on the product
P#i#ity
P#i#ity
0ased upon input from users regarding
0ased upon input from users regarding
which defects are most important to them'
which defects are most important to them'
and be fi#ed first
and be fi#ed first

Srihari Techsoft
Se,e#ity Le,el!
Se,e#ity Le,el!

Critical
Critical

*a!or 5 /igh
*a!or 5 /igh

&verage 5 *edium
&verage 5 *edium

*inor 5 low
*inor 5 low

Cosmetic defects
Cosmetic defects

Srihari Techsoft
Se,e#ity Le,el 1 C#iti&al
Se,e#ity Le,el 1 C#iti&al

&n installation process which does not load a

&n installation process which does not load a
component
component

& missing menu option

& missing menu option

Security permission required to access a function

Security permission required to access a function
under test
under test

;unctionality does not permit for further testing

;unctionality does not permit for further testing

Srihari Techsoft

.untime "rrors li$e NavaScript errors etc

.untime "rrors li$e NavaScript errors etc

;unctionality *issed out 5 Incorrect

;unctionality *issed out 5 Incorrect
Implementation (*a!or Deviation from
Implementation (*a!or Deviation from
.equirements)
.equirements)

Performance Issues (If specified by Client)

Performance Issues (If specified by Client)

0rowser incompatibility and Operating systems

0rowser incompatibility and Operating systems
incompatibility issues depending on the impact
incompatibility issues depending on the impact
of error
of error

Dead -in$s
Dead -in$s

Srihari Techsoft
Se,e#ity Le,el 1 2a;# ? Hi'h
Se,e#ity Le,el 1 2a;# ? Hi'h

.eboot the system

.eboot the system

%he wrong field being updated

%he wrong field being updated

&n updated operation that fails to complete

&n updated operation that fails to complete

Performance Issues (If not specified by Client)

Performance Issues (If not specified by Client)

*andatory Halidations for *andatory ;ields

*andatory Halidations for *andatory ;ields

Srihari Techsoft

;unctionality incorrectly implemented (*inor

;unctionality incorrectly implemented (*inor
Deviation from .equirements)
Deviation from .equirements)

Images' Jraphics missing which hinders

Images' Jraphics missing which hinders
functionality
functionality

;ront "nd 5 /ome Page &lignment issues

;ront "nd 5 /ome Page &lignment issues

Severity -evel 3 &verage 5 *edium

Severity -evel 3 &verage 5 *edium
Incorrect5missing hot $ey operation
Incorrect5missing hot $ey operation

Srihari Techsoft
Se,e#ity Le,el 1 2i$# ? L+
Se,e#ity Le,el 1 2i$# ? L+

*isspelled or ungrammatical te#t

*isspelled or ungrammatical te#t

Inappropriate or incorrect formatting (such as

Inappropriate or incorrect formatting (such as
te#t font' si1e' alignment' color' etc)
te#t font' si1e' alignment' color' etc)

Screen -ayout Issues

Screen -ayout Issues

Spelling *ista$es 5 Jrammatical *ista$es

Spelling *ista$es 5 Jrammatical *ista$es

Documentation "rrors
Documentation "rrors

Srihari Techsoft

Page %itles *issing

Page %itles *issing

&lt %e#t for Images

&lt %e#t for Images

0ac$ground Color for the Pages other than

0ac$ground Color for the Pages other than
/ome page
/ome page

Default Halue missing for the fields required

Default Halue missing for the fields required

Cursor Set ;ocus and %ab ;low on the Page

Cursor Set ;ocus and %ab ;low on the Page

Images' Jraphics missing' which does not'

Images' Jraphics missing' which does not'
hinders functionality
hinders functionality

Srihari Techsoft
Te!t Re"#t!
Te!t Re"#t!
D INTERI2 REPORTS
D INTERI2 REPORTS

;unctional %esting Status

;unctional %esting Status

;unctions :or$ing %imeline

;unctions :or$ing %imeline

"#pected Hs &ctual Defects Detected %imeline

"#pected Hs &ctual Defects Detected %imeline

Defects Detected Hs Corrected Jap %imeline

Defects Detected Hs Corrected Jap %imeline

&verage &ge of Detected Defects by type

&verage &ge of Detected Defects by type

Defect Distribution
Defect Distribution

.elative Defect Distribution

.elative Defect Distribution

%esting &ction
%esting &ction

0u$&ti$al Te!ti$' Statu! Re"#t
.eport shows percentage of the
functions that are
,
;ully %ested
,
%ested with Open defects
,
6ot %ested

Srihari Techsoft
0u$&ti$! 8#=i$' Timeli$e
0u$&ti$! 8#=i$' Timeli$e

.eport shows the actual plan to have all

.eport shows the actual plan to have all


functions verses the current status of the
functions verses the current status of the


functions wor$ing
functions wor$ing

-ine graph is an ideal format

-ine graph is an ideal format

Srihari Techsoft
EA"e&te- 9!* A&tual De%e&t! Dete&te-
EA"e&te- 9!* A&tual De%e&t! Dete&te-

&nalysis between the number of defects being

&nalysis between the number of defects being


generated against the e#pected number of
generated against the e#pected number of


defects e#pected from the planning stage
defects e#pected from the planning stage

Srihari Techsoft
De%e&t! Dete&te- 9!* C##e&te- <a"
De%e&t! Dete&te- 9!* C##e&te- <a"


& line graph format that shows the
& line graph format that shows the

6umber of defects uncovered verses the

6umber of defects uncovered verses the


number of defects being corrected and
number of defects being corrected and


accepted by the testing group
accepted by the testing group

Srihari Techsoft
A,e#a'e A'e Dete&te- De%e&t! .y Ty"e
A,e#a'e A'e Dete&te- De%e&t! .y Ty"e

&verage days of outstanding defects by its

&verage days of outstanding defects by its


severity type or level
severity type or level

%he planning stage provides the acceptable

%he planning stage provides the acceptable


open days by defect type
open days by defect type

Srihari Techsoft
De%e&t Di!t#i.uti$
De%e&t Di!t#i.uti$
Shows defect distribution by function or module
Shows defect distribution by function or module
and the number of tests completed
and the number of tests completed
Relati,e De%e&t Di!t#i.uti$
Relati,e De%e&t Di!t#i.uti$

6ormali1e the level of defects with the

6ormali1e the level of defects with the


previous reports generated
previous reports generated

6ormali1ing over the number of functions or

6ormali1ing over the number of functions or


lines of code shows a more accurate level of
lines of code shows a more accurate level of


defects
defects

Srihari Techsoft
Te!ti$' A&ti$
Te!ti$' A&ti$
Re"#t !h+!
Re"#t !h+!

Possible shortfalls in testing

Possible shortfalls in testing

6umber of severity+@ defects

6umber of severity+@ defects

Priority of defects
Priority of defects

.ecurring defects
.ecurring defects

%ests behind schedule

%ests behind schedule
G
G
and other information that present an accurate
and other information that present an accurate
testing picture
testing picture

2ETRICS
2ETRICS
4 Ty"e!

Product metrics

Process metrics

Srihari Techsoft
P#&e!! 2et#i&!

*easures the characteristic of the

,
methods
,
techniques
,
tools

Srihari Techsoft
P#-u&t 2et#i&!

2easures the characteristic of the

documentation and code

Srihari Techsoft
Te!t 2et#i&!
U!e# Pa#ti&i"ati$ C User Participation test time
9!* %otal test time
Path Te!te- E 6umber of path tested 9!* %otal
number of paths
A&&e"ta$&e &#ite#ia te!te- C &cceptance criteria
verified 9!* %otal acceptance criteria

Srihari Techsoft
Te!t &!t C %est cost 9!* %otal system cost
C!t t l&ate -e%e&t C %est cost 5 6o of defects
located in the testing

Dete&te- "#-u&ti$ -e%e&t C 6o of defects
detected in production 5 &pplication system si1e
Te!t Autmati$ C Cost of manual test effort 5
%otal test cost

Srihari Techsoft
C22 1 Le,el 3 1 I$itial Le,el
C22 1 Le,el 3 1 I$itial Le,el
The #'a$i(ati$
The #'a$i(ati$

Does not have an environment for developing

Does not have an environment for developing
and maintaining software
and maintaining software

&t the time of crises' pro!ects usually stop

&t the time of crises' pro!ects usually stop
using all planned procedures and revert to
using all planned procedures and revert to
coding and testing
coding and testing

Srihari Techsoft
C22 1 Le,el 4 1 Re"eata.le le,el
C22 1 Le,el 4 1 Re"eata.le le,el
"ffective management process having
"ffective management process having
established which can be
established which can be

Practiced
Practiced

Documented
Documented

"nforced
"nforced

%rained
%rained

*easured
*easured

Improvised
Improvised

Srihari Techsoft
C22 1 Le,el 5 1 De%i$e- le,el
C22 1 Le,el 5 1 De%i$e- le,el

Standard defined software engineering and

Standard defined software engineering and
management process for developing and
management process for developing and
maintaining software
maintaining software

%hese processes are put together to ma$e a

%hese processes are put together to ma$e a


coherent whole
coherent whole

Srihari Techsoft
C22 1 Le,el 6 1 2a$a'e- le,el
C22 1 Le,el 6 1 2a$a'e- le,el

Iuantitative goals set for both software products

Iuantitative goals set for both software products
and processes
and processes

%he organi1ational measurement plan involves

%he organi1ational measurement plan involves
determining the productivity and quality for all
determining the productivity and quality for all
important software process activities across all
important software process activities across all
pro!ects
pro!ects

Srihari Techsoft
C22 1 Le,el 7 1 O"timi(i$' le,el
C22 1 Le,el 7 1 O"timi(i$' le,el
"mphasis laid on
"mphasis laid on

Process improvement
Process improvement

%ools to identify wea$nesses e#isting in their

%ools to identify wea$nesses e#isting in their


processes
processes

*a$e timely corrections

*a$e timely corrections


Srihari Techsoft
TESTIN< STANDARDS
TESTIN< STANDARDS
EAte#$al Sta$-a#-!
EAte#$al Sta$-a#-!

;amiliarity with and adoption of industry test
;amiliarity with and adoption of industry test
standards from organi1ations
standards from organi1ations
I$te#$al Sta$-a#-!
I$te#$al Sta$-a#-!

Development and enforcement of the test
Development and enforcement of the test
standards that testers must meet
standards that testers must meet

Srihari Techsoft
IEEE STANDARDS
IEEE STANDARDS
Institute of "lectrical and "lectronics
Institute of "lectrical and "lectronics
"ngineers designed an entire set of standards
"ngineers designed an entire set of standards
for software and to be followed by the
for software and to be followed by the
testers
testers

Srihari Techsoft
IEEE
IEEE
3
3
Standard Jlossary of Software "ngineering
Standard Jlossary of Software "ngineering
%erminology
%erminology
IEEE
IEEE
3
3
Standard for Software Iuality &ssurance Plan
Standard for Software Iuality &ssurance Plan
IEEE
IEEE
3
3
Standard for Software Configuration
Standard for Software Configuration
*anagement Plan
*anagement Plan
IEEE
IEEE
3
3
Standard for Software for Software %est
Standard for Software for Software %est
Documentation
Documentation
IEEE
IEEE
3
3
.ecommended Practice for Software
.ecommended Practice for Software
.equirement Specification
.equirement Specification

Srihari Techsoft
IEEE
IEEE
3
3
Standard for Software Unit %esting
Standard for Software Unit %esting
IEEE
IEEE
3
3
Standard for Software Herification and
Standard for Software Herification and
Halidation
Halidation
IEEE
IEEE
3
3
Standard for Software .eviews
Standard for Software .eviews
IEEE
IEEE
3
3
.ecommended practice for Software
.ecommended practice for Software
Design descriptions
Design descriptions
IEEE
IEEE
3
3
Standard Classification for Software
Standard Classification for Software
&nomalies
&nomalies

Srihari Techsoft
IEEE
IEEE
3
3
Standard for Software Productivity
Standard for Software Productivity
metrics
metrics
IEEE
IEEE
3
3
Standard for Software Pro!ect
Standard for Software Pro!ect
*anagement plans
*anagement plans
IEEE
IEEE
3
3
Standard for Software *anagement
Standard for Software *anagement
IEEE
IEEE
3
3
Standard for Software Iuality *etrics
Standard for Software Iuality *etrics
*ethodology
*ethodology

Srihari Techsoft
Othe# !ta$-a#-!F**
Othe# !ta$-a#-!F**
ISO
ISO
3
3
International Organi1ation for Standards
International Organi1ation for Standards
SiA Si'ma
SiA Si'ma
3
3
Oero Defect Orientation
Oero Defect Orientation
SPICE
SPICE
3
3
Software Process Improvement and
Software Process Improvement and
Capability Determination
Capability Determination
NIST
NIST
3
3
6ational Institute of Standards and
6ational Institute of Standards and
%echnology
%echnology