Bug Reports
How to write bug reports, the difference between severity and priority, bug statuses and best practices.
Questions and explanations
Find an explanation for each question here. To test yourself, take the quiz above first.
What is a bug's Severity?
Severity shows how seriously a defect disrupts the system's operation: from Blocker/Critical (the system doesn't work) to Trivial (a cosmetic detail).
What is a bug's Priority?
Priority determines how urgently a bug needs to be fixed relative to other tasks — this decision is usually made more by the business/product manager than by QA alone.
There is a typo at the bottom of a website. An ad campaign starts tomorrow. How should this bug be assessed?
The typo doesn't break functionality (low severity), but because of the upcoming ad launch it needs to be fixed urgently (high priority) — a classic example of severity and priority not matching.
Users cannot pay for an order. How should this bug be assessed?
The bug blocks a key business function (payment) for all users — it's both technically critical (severity) and requires an immediate fix (priority).
The application does not open because of an error. What Severity does this bug have?
Blocker (or Critical) is the highest severity level: the bug makes the application or a key part of it unusable and often blocks further testing.
Why is it important to include precise steps to reproduce in a bug report?
Without clear, reproducible steps, the developer may not be able to reproduce the bug, and the report will come back marked "Can't Reproduce", wasting time for both sides.
Why is it recommended to file one bug report per issue, instead of combining several different bugs into one report?
If a single report contains several different problems, they may have different severity/priority and different fix timelines — separate bugs are easier to prioritize, test, and close independently.
What should go in the "Actual result" section of a bug report?
Actual result describes what really happened (e.g., "a 500 error appeared"), while Expected result describes how the system should have behaved per the requirements. Comparing the two reveals the essence of the bug.
Why should a bug report include the environment (OS, browser, app version, device)?
Many bugs only reproduce on a specific OS, browser version, or device — without this information it's much harder for a developer to pinpoint the cause and scope of the problem.
What should a good bug report title look like?
A title should let someone quickly grasp the essence of the problem without reading the whole report — vague titles like "Broken" make prioritization and duplicate detection harder.
Why attach screenshots, video, or logs to a bug report?
Visual evidence and logs help the developer immediately see the problem and its context (error stack, network state, etc.), without wasting time trying to reproduce the bug blindly.
Which set of severity levels is typically used in most bug trackers?
Severity is usually graded from Blocker/Critical (the system is unusable) through Major and Minor down to Trivial (a cosmetic detail). P0–P3 levels are more often used for Priority, while New/Assigned/Fixed/Closed are bug life cycle statuses.
Can a bug have high Severity but low Priority?
Severity and Priority are independent of each other: a bug can seriously break rarely used functionality (high severity) but not be urgent for the business right now (low priority), for example if that feature is about to be removed.
Who usually sets a bug's Severity, and who sets its Priority?
Severity is a technical assessment of a bug's impact, usually given by the tester. Priority is a business decision about fix order, and a product manager or team lead is often involved here.
Which of the following is a bad practice when writing a bug report?
Vague statements with no specifics don't let the developer understand and reproduce the problem — a good bug report always contains concrete, verifiable details.
A user cannot register, but the website opens. What is the bug's Severity?
A broken core feature like registration is a serious problem (Critical), but since the rest of the site remains usable, it doesn't fully block the application — so it's not a Blocker.
A button is slightly misplaced but works. What is the bug's Severity?
A minor visual misalignment that doesn't affect functionality is typically classified as Minor severity.
There is a spelling mistake in a text. What is the bug's Severity?
A spelling mistake is a cosmetic issue that doesn't affect functionality, so it's typically classified as Trivial severity.
What is bug triage?
Bug triage is the process where the team regularly reviews newly reported bugs, decides on their severity/priority, and assigns them to the right people to fix.
What is the actual result in a bug report?
The actual result describes the application's real behavior. It is compared with the expected result to determine whether there is a bug.
Is there a bug if the actual and expected results match?
A bug exists when the actual result differs from the expected result. If they match, the check passed successfully.
Steps to reproduce are part of what?
Steps to reproduce are part of a bug report. They help a developer repeat the problem and verify the fix.