26-07-2012, 03:52 PM
Defect Tracking and Management
DefectTrackingandManagement.ppt (Size: 161 KB / Downloads: 119)
Defect Management
A major test objective is to identify defects. Once identified, defects need to be recorded, monitored, reported and corrected.
The primary goal is to prevent defects.
The defect management process like the entire software development process, should be risk driven, i.e., strategies, priorities and resources should be based on an assessment of the risk.
Defect measurement should be integrated into the development process and be used by the project team to improve the development process
Defect information should be used to improve the process
Imperfect or flawed processes cause most defects.
Defect Management Process
The steps below describe a simple defect tracking process:
Execute the test and compare the actual results to the documented expected results.
If a discrepancy exists, log the discrepancy with a status of “open”. Supplementary documentation, such as screen prints or program traces, should be attached if available.
The test manager or tester should review the problem log with the appropriate member of the development team to determine if the discrepancy is truly a defect.