Software testing

Developed by
Lilaram Anjane

Contents
Verification and Validation
Severity and priority
Bug life cycle

Verification

The process of evaluating work products(not the

actual final product) of a development phase to
determine whether they meet the specified
requirements for that phase.
To ensure that the product is being built according
to the requirements and design specifications. In
other words, to ensure that work products meet
their specified requirements.
Software must conform to its specification

Are we building the product

right?

Activities or method for verification

i)Walkthroughs
ii)Inspections
iii)Reviews
Evaluation Items
i)Plans
ii)Requirement specifications
iii)Design specifications
iv) Code and test cases

Validation
The process of evaluating software during or at the
end of development process to determine
whether
it
satisfies
specified
business
requirements.
To ensure that the product actually meets the
Users needs, and that the specifications were in
the first place . In other words, to demonstrate
that the product fulfills its intended use when
placed in its intended environment.
Software should do what the user really requires

Are we building the right Product?

Activities or method of validationTesting

Evaluation Items in ValidationActual product or software

Verification
Validation

Static technique
Non execution of
code.
Human base
checking of
document or files.

Dynamic technique

Execution of code

Computer base
execution of
program

Verification
Validation

Verification uses
methods like
inspections,
reviews,
walkthroughs, and
Desk- checking

Validation
uses
methods like black
box
(functional)
testing, gray box
testing, and white
box
(structural)
testing etc.

Verification
Validation

Verificationis to
check whether the
software conforms
to specifications.

It can catch errors

that validation
cannot catch. It is
low level exercise.

Validationis to
check whether
software meets the
customer
expectations and
requirements.

It can catch errors

that verification
cannot catch. It is
High Level Exercise.

Verification

Target is
requirements
specification,
application and
software
architecture, high
level, complete
design, and
database design
etc.

Validation

Target is actual
product-a unit, a
module, a bent of
integrated
modules, and
effective final
product.

Verification
Validation

Verification is done
by QA team to
ensure that the
software is as per
the specifications
in the SRS
document.

Validation is
carried out with
the involvement of
testing team.

Severity

Attribute of defect or bug.

Impact that a given defect has on the system.

the severity is defined in terms of financial

loss, damage to environment, companys
reputation and loss of life.
We can measure the severity as Critical,
high,
Medium, Low.

Priority

Priority defines the order in which we should

resolve a defect.

Should we fix it now, or can it wait?

This priority status is set by the tester to the

developer mentioning the time frame to fix
the defect.

Combinations of severity and priority

1) High severity, High priority Bug.

2)High severity, low priority Bug.

3)low severity, high priority Bug.

4)low severity, low priority Bug.

Defect Life Cycle