How should you use screenshots and recordings in bug reports?

• A. Omit visuals entirely.
• B. Annotate with unrelated timestamps.
• C. Use low-resolution visuals only.
• D. Include high-quality visuals that clearly illustrate the issue; annotate with relevant timestamps.

Answer: (D)

Clear visuals in bug reports provide concrete evidence of what went wrong. High-quality screenshots or screen recordings capture the exact UI state, error messages, and the sequence of actions, so reviewers can see the issue as it occurs rather than relying on memory or vague descriptions. Annotating these visuals with relevant timestamps helps map what’s shown to specific steps, logs, or events, making reproduction and verification faster and more reliable. Omitting visuals removes critical context, while annotating with timestamps that aren’t related to the issue can confuse rather than clarify, and low-resolution visuals may miss details like small text or subtle UI changes. When paired with concise steps to reproduce and environment details, these visuals turn a vague report into a precise, actionable defect.