Software Testing Online Training
DEFECT TRACKING
&
CORRECTION
www.garudatrainings.com
What is defect…?
“A defect is an operation or function that fails to
meet the products specification…. To be precise a
defect is any non-conformity in a software
product or process”
www.garudatrainings.com
defect discovery process…
 The defect discovering process
enables us to identify defects.
 This process involves reveling
defects and bringing the defect
to the notice of the development team.
 The development team then acknowledges the defect as
valid and fix the defect.
 The tester verifies and close the defect in the end.
www.garudatrainings.com
defect tracking life cycle…
Raising a defect
TESTER
Reporting a defect
Acknowledging the defect
Fixing the defect
D
E
V
E
L
O
P
E
R
Verifies fixes internally
Verifies the fixes
Closing or reopening defect based on
the defect status
www.garudatrainings.com
T
E
S
T
E
R
finding defects…
 Every software development project plans for a set of activities that
are specially designed and performed to uncover defects.
 There are three broad categories for detecting defects.
 Static technique Every software development project plans for a set
of activities that are specially designed and performed to uncover
defects.
 There are three broad categories for detecting defects.
Involves performing manual intermediate checks to examine the
quality of the product being developed.
Refers to the process of executing software test to find defects.
Involves end users testing the system at the operational level
and discovering defects that are not identified during the testing
process.
www.garudatrainings.com
The three category
of defect finding
techniques are
jointly required for
an effective defect
management
program in an
organization.
Static
Dynamic
“Static technique are more effective at finding defects
in the early phase of the SDLC”
www.garudatrainings.com
Operational
categorizing defects…
On the basis of
•Functionality
•Severity
•Priority
www.garudatrainings.com
On the Basis of
functionality
 Interface- related
 Navigational
 Functional
www.garudatrainings.com
On the Basis of severity
 High Severity
 Medium severity
 Low severity
www.garudatrainings.com
High Severity
Signifies that a minor issue occurred that costs
some loss of functions. However workaround
and testing can proceed without interruption.
Medium Severity
Low Severity
www.garudatrainings.com
on the basis of priority…
 High priority
 Medium priority
 Low priority
Signifies that a defect has a major impact
Signifies that a defect has a major impact
on the customer. The problem should be
on the customer. This must be immediately
fixed before the release of the current
fixed
Signifies
a defect has a minor impact on the customer. The
versionthat
in development
flaw should be fixed if there is time, but it can be deferred until
the next release.
www.garudatrainings.com
acknoWledging defects…
 Acknowledging defects is common in
software testing environment
 Even though defect acknowledgment is a
crucial stage in the defect life cycle, there
are often delays in the process.
 One of the prominent reasons for delays in
the acknowledgment of the defect is when
the testing team is unable to replicate the
defect report for the development team
www.garudatrainings.com
Defect management process
 The defect management process, involves defect
recording, defect reporting, keeping track of the
defect using defect tracking tool.
 Defect recording
defects are identified and recorded
at each stage of the testing process.
www.garudatrainings.com
Why to record???
 4 purpose
 To correct the defect
 To report the status of the application
 To gather statistics
 To further improve for software development process
www.garudatrainings.com
Defect reporting
 A defect report describes those which are
present in the software..
 A defect report should provide complete
information on the defect to both the
testing team and the team responsible for
fixing the defect.
www.garudatrainings.com
Contents of defect report












A unique identification no. for the defect.
The defect name and type.
Source of the defect
Severity of the defect.
Priority assigned to the defect.
The current status of the defect.
Detailed description of the defect.
The platform and operating system implemented.
The steps performed when the defect occurs.
The location of the defect with screen shots.
The Person responsible for testing.
The person responsible for fixing the defect.
www.garudatrainings.com
Register for a Free DEMO
 www.Garudatrainings.com
 +1 508-841-6144
 [email protected]
[email protected]
www.garudatrainings.com