Bug report grader: score a report on 8 criteria
Paste one bug report from your tracker, Discord or e-mail. The grader checks 8 things a programmer needs before they can reproduce the bug, scores the report and tells you what to add. The criteria are the fields of our sample QA report.
Everything runs in your browser; nothing is uploaded.
Verdict
Book a Smoke Test call See a full sample report
Reports from a Jumbo Jelly Smoke Test (€290, 1 tester, 8 hours) score 8/8 by construction: that is the format we use.
The 8 criteria
| # | Criterion | What the grader looks for |
|---|---|---|
| 1 | Title: what, where, when | A first line of 25–140 characters. |
| 2 | Numbered steps | At least two lines starting with a number or “Step”. |
| 3 | Expected result | “Expected:” or a sentence with “should”. |
| 4 | Actual result | “Actual:” or “instead”, “what happens”. |
| 5 | Build, branch, version | “build”, “version”, “branch” or a version number. |
| 6 | Hardware, OS, input | A GPU, CPU, RAM, OS, resolution or input device. |
| 7 | Reproducibility | “4/5”, a percentage, or always / sometimes / once. |
| 8 | Attachment | Video, screenshot, log, crash dump or save file. |
The checks are keyword heuristics, so a well-written report in unusual wording can score lower than it deserves, and a report that name-drops every field can score higher. Use it as a nudge, not a judge. How to brief testers so reports arrive in this shape: How to write a QA brief.