Defect Tracking and

Management

CBOK Domain 13
By Marjie Danckert,CQA

1
12/02/09
Overview
 Defect Recording
 Defect Reporting
 Defect Tracking
 Testing Defect Correction

2
12/02/09
What is a defect?
 From the producer’s point of view: a
deviation from specifications, whether
missing, wrong, or extra.
 From the customer’s point of view:
anything that causes customer
dissatisfactions, whether in the
requirements or not.

3
12/02/09
The point of writing
Problem Reports is to get
bugs fixed.

Testing Computer Software

4
12/02/09
Defect Recording
 Used to describe and quantify deviations
from requirements
 Defects are recorded to:
– Correct the defect
– Report the status of the application
– Gather statistics used to develop defect
expectations in future applications
– Improve the software development process
5
12/02/09
Identifier Date and time of changes

Descriptive defect name Detailed description

Source of defect Program defect found

Severity Screen prints, logs, etc.

Priority Stage of origination

Status Person assigned

6
12/02/09
Tips for good recording
 Summary:
– Emphasizes impact
– First impression
 Description:
– Accurate, complete and concise
– Steps to reproduce
– Isolation information

7
12/02/09
Tools
 Simple: spreadsheet, whiteboard
 Database
 Specialized Products
– Customized fields
– Reporting
– Email notification
– Graphing

8
12/02/09
The best tester isn’t the
one who finds the most
bugs or who
embarrasses the most
programmers. The best
tester is the one who
gets the most bugs fixed.
9
12/02/09
Defect Reporting
 Report the status of defects; including
severity and location.
 Severity should be predefined for
consistency: data corruption, system crash,
security violation
 Priority determines the order they get fixed
(usually subjective).

10
12/02/09
Defect Tracking
 Monitoringdefects form the time of
recording until satisfactory resolution has
been determined.

11
12/02/09
Testing Defect Correction
 Validation – ensure changes compliant
with requirements
 Regression Testing – ensure unchanged
functionality performs correctly
 Verification – ensuring affected
documentation is updated

12
12/02/09
Regression Testing
 Unit Regression Testing: single
component
 Regional Regression Testing: modules /
areas connected to changed component
 Full Regression Testing: entire application

13
12/02/09
Where to Get More Information
 Effective Methods for Software Testing
– William Perry
 Managing the Testing Process
– Rex Black
 Testing Computer Software
– Kaner, Falk, Nguyen
 StickyMinds.com

14
12/02/09