Understanding Attributes of a Good Bug Report
A well-written bug report is crucial for ensuring that issues in software development are accurately identified, understood, and resolved efficiently. The following attributes are key to creating an effective bug report.
Exam Question
Which are attributes of a good bug report?
(choose all that apply)
A. Expected results and observed results.
B. Clear title and proper grammar in report.
C. Build/version where bug was found.
D. One bug per report.
E. Provides simple and repeatable reproduction steps.
F. Screenshots or other pictures of bug in action when user interfaces are involved.
Correct Answers
A. Expected results and observed results.
B. Clear title and proper grammar in report.
C. Build/version where bug was found.
D. One bug per report.
E. Provides simple and repeatable reproduction steps.
F. Screenshots or other pictures of bug in action when user interfaces are involved.
Explanation
Correct Answers
A. Expected results and observed results:
A good bug report clearly states what the expected outcome was versus what actually happened. This comparison helps developers understand the issue and determine the deviation from expected behavior.
B. Clear title and proper grammar in report:
A clear and concise title helps quickly identify the nature of the bug. Proper grammar ensures the report is understandable, reducing the likelihood of miscommunication.
C. Build/version where bug was found:
Specifying the build or version where the bug was discovered helps in reproducing the issue and understanding whether it affects current or past versions of the software.
D. One bug per report:
Each bug report should focus on a single issue. This makes it easier to track, prioritize, and resolve each problem without confusion.
E. Provides simple and repeatable reproduction steps:
Reproduction steps are critical in helping developers recreate the issue consistently, making it easier to diagnose and fix.
F. Screenshots or other pictures of bug in action when user interfaces are involved:
Visual aids like screenshots or videos can be extremely helpful, especially for UI-related bugs, as they provide a clear representation of the issue.
Relevance to the PSD Exam
Understanding the attributes of a good bug report is important for the PSD exam. This knowledge helps ensure that issues are communicated effectively, enabling the team to address them efficiently.
Key Takeaways
- Clarity: Use clear titles, grammar, and structured reports to ensure easy understanding and communication.
- Reproducibility: Provide detailed steps to reproduce the bug to assist developers in identifying and fixing the issue.
- Specificity: Focus on one bug per report and include relevant details like build/version, expected vs. observed results, and visual aids when necessary.
Conclusion
A good bug report is essential for effective communication and resolution of software issues. By ensuring that bug reports are clear, detailed, and focused, teams can address problems more quickly and efficiently.

Get ready for the official PSD exam
127 PSD practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSD exam fee ($200) is paid separately to Scrum.org.
More PSD exam questions
- Which types of tests can be automated?
- Should User Stories be part of the documentation generated by a Scrum project?
- The Definition of Done describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Developers do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?
- What is the value of refactoring code?
- Who must be present at the Daily Scrum meeting?
