You have been seeing a high number of rejections of defect reports The developers are complaining that they do not understand what the problem is…

Context Analysis:

Long descriptive paragraphs are difficult to parse, even if they contain all necessary information.

Developers need concise, structured information for quick understanding.

Evaluation of Options:

A . Instruct your team to make all defects high priority:

Incorrect. Changing priority does not address the clarity issue in defect reports.

B . Highlight all the information and walk through it with the developers:

Incorrect. This is time-consuming and not scalable as a general solution.

C . Email screenshots to developers in addition to attaching them to defect reports:

Incorrect. Duplication of information does not solve the clarity problem.

D . Separate out the steps to reproduce the defect in the description so it is clearer for the developers

and easier to find:

Correct. Structuring defect reports improves clarity and makes them easier to process.

Syllabus Alignment:

ISTQB recommends clear and concise defect reports to facilitate understanding and resolution (TM-

2.3.5).

Reference:

ISTQB Advanced Level Test Management Syllabus (TM-2.3.5)