A defect report is a document that records the details of a defect found during testing. A defect report typically contains the following items:
Identifier: A unique identifier for the defect report
Summary: A concise summary of the defect
Description: A detailed description of the defect, including the steps to reproduce it, the expected and actual results, and any relevant screenshots or logs
Severity: The degree of impact that the defect has on the system
Priority: The level of urgency for resolving the defect
Status: The current state of the defect, such as new, open, resolved, closed, etc.
Resolution: The action taken to resolve the defect, such as fix, workaround, reject, etc. Out of these items, the one that is not needed to specify in a defect report is how to fix the defect. How to fix the defect is a technical solution that is usually determined by the developer who is assigned to resolve the defect. How to fix the defect is not part of the defect report, but rather part of the code change or patch that is delivered to fix the defect. The other items are needed to specify in a defect report, as they provide essential information for identifying, tracking and resolving defects. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 3, page 32-33.
Submit