Defect Report
A defect report is a document that records information about a defect so it can be analyzed, reproduced, corrected, and verified.
“Documentation of the occurrence, nature, and status of a defect.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Defect Report?
A defect report communicates everything needed to understand, reproduce, prioritize, and resolve a defect. High-quality reports reduce investigation time and improve collaboration between testers and developers.
Essential information: A defect report typically includes steps to reproduce, expected and actual results, severity, priority, and environment details.
Purpose: Well-written reports help developers reproduce defects quickly and accurately.
Lifecycle support: Defect reports remain part of the project's defect history and quality metrics.
Real World Example
A hospital medication system shows a different dosage warning in test than the one specified by the clinical safety rule.
The team needs precise language to separate what was observed, what should have happened, and whether the difference represents a reportable issue. Defect report provides that distinction.
The tester records the steps, data, observed behavior, expected behavior, and evidence so triage can focus on patient safety impact instead of vague descriptions.
The issue is handled faster because Defect report helps everyone discuss the problem using a shared testing vocabulary.
Practice Questions
Question 1
Which statement BEST describes Defect report in the context of ISTQB terminology?
Question 2
A tester needs to explain Defect report to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Defect Report. Test your understanding with topic-specific questions in our Mock Exams.