What is a defect?
A defect is any error found by testing and reviewing activities (All errors found by internal reviewer, external reviewer and customer).
If you consider any recommendations to fix, this recommendation should be logged as a defect in defined tool (an excel file, a defect management tool).
What should be done after a defect is found?
The defect needs to be logged and assigned to developers that can fix it
After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn’t create problems elsewhere
Defect management should encapsulate these processes.
Concepts
Defect logging: the initial reporting and recording of a discovered defect.
Defect tracking: monitors and records what happened to each defect after its initial discovery, up until its final resolution. Tracking via defect status
Defect Status: describe current status of logged defect
Defect Lifecycle
Defect Status:
OPPENED
The defect is not fixed, or fixed but not satisfactorily as required
ASSIGNED
The defect is reviewed and assigned to fix it
FIXED
The defect is already fixed and waiting to retest
CLOSED
The defect is fixed satisfactorily as required
ACCEPTED
The defect has not been fixed satisfactorily as required, but it’s accepted by concession of authority or customer
CANCELLED
It’s not a defect or defect is removed by actions other than bug fixing
>>>> DEFECT MANAGERMENT
Using template to log and track defect
Log defect effectively
Template defects Log
Defect ID: index the defect to manage easily
Module: address defect location (module name, function name)
Description: descript defect found (as detail as much)
Type: select defect type
Severity: select defect severity
Priority: select defect priority
Status: select defect status
Created Date: input the date defect found
Assigned To: name of person, who is assigned to fix defect
Corrective Action: actions to fix assigned defect
