Bug Report and Arguing with a Developer
Quiz: bug report structure, severity and priority, steps to reproduce, environment and the “it works for me” reply.
Questions and explanations
Find an explanation for each question here. To test yourself, take the quiz above first.
Which bug report title is the best?
A good title briefly answers where, during which action and what went wrong. A developer understands the point without opening the description.
What goes into the “Actual result” field?
The actual result is an observation. The developer looks for the cause. The correct behaviour is described separately in the “expected result”.
How do you briefly explain the difference between severity and priority?
Severity describes the scale of consequences for the product, priority describes the order of fixing from the business’s point of view. Usually QA sets severity, and a product manager or the team sets priority.
An interviewer asks for an example of a bug with high severity but low priority. Which one fits?
A crash is high severity, but if the page is almost never used, the fix can wait. A typo on the home page is the opposite: low severity but high priority. The sign-in bug is high on both.
Which steps to reproduce are considered good?
A developer should be able to repeat the bug from the steps without extra questions. Concrete values are needed (for example, user type or amount), but no unnecessary actions.
What is usually included in the environment of a bug report?
Many bugs reproduce only in a particular browser, on a specific version or on one of the environments. Without the environment, a developer may waste time.
A developer replies to your bug: “It works for me.” What is the best next step?
Most often the cause is a difference in environment, data or version. Calmly figuring it out together is faster and more useful than arguing or escalating.
Which wording in a bug report is a mistake?
“Strangely” and “terribly” are subjective judgements and cannot be verified. A bug report needs observable facts: what you clicked, what you saw, which values you got.