1.9Exercises

Take your three most recent bug reports and rewrite the titles using observation-oriented framing. Compare the originals with the rewrites and note how the tone changes.
Audit one bug report using the CLEAR framework. Create a checklist and mark which elements are present and which are missing.
Rewrite the following bug report using the CLEAR framework: "The upload doesn't work for big files. It just spins forever."

Identify one bug you filed that should have been a conversation first, and one conversation you had that should have been a bug report. Write a brief explanation of why.
Ask a developer on your team: "What makes a bug report easy or hard for you to work with?" Document their response and identify one change you can make based on their feedback.
Write two versions of a bug report for the following scenario: A user can add more than 99 items to their cart despite the UI showing a max of 99. Write a blame-oriented version and then an observation-oriented version.

Review your team's bug reporting template and propose three improvements based on the material in this chapter. Present them at your next team meeting.
Create a bug reporting style guide for your team that addresses cultural differences. Include examples for both direct and indirect communication styles.
Design a "bug report quality" rubric that you could use to mentor junior QA engineers. Include scoring criteria for title quality, reproduction clarity, tone, and completeness.