Identifying metrics to improve the defect reporting process by reducing ambiguities or improving accuracy.
Evaluation of Options:
A. Number of defect reports re-opened:
Incorrect. This reflects issues with defect resolution rather than reporting.
B. Number of defects in a particular area of the code:
Incorrect. This metric pertains to defect clustering, not the reporting process.
C. Number of defect reports rejected by the developers:
Correct. Rejected reports often indicate poor reporting quality (e.g., insufficient details, incorrect categorization), directly highlighting areas for improvement.
D. Number of defects found in a phase later than they were introduced:
Incorrect. This is a measure of defect detection efficiency, not reporting quality.
Syllabus Alignment:
The syllabus stresses the importance of using defect metrics to refine processes, including reporting accuracy (TM-2.3.5).
References:
ISTQB Advanced Level Test Management Syllabus (TM-2.3.5)​
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit