Skip to content
Independent guides for QA & test automationRSSEditorial policy
QA Vibes

Free tool

Bug report grader

Paste a bug report and see what a developer will ask you for before they can fix it. The checks follow the structure in our guide to writing high-quality bug reports.

Severity is how bad the impact is. Priority is how soon to fix it. A typo on the checkout button can be Minor severity but P1.

Grading runs entirely in your browser. Nothing you paste is sent anywhere.

15

Score / 100

Will bounce back

  • Specific title

    Partial · 5/10

    Title is short. Say what fails and where, e.g. “Invoice CSV export returns 500 for admin accounts”. Why this matters

  • Numbered steps to reproduce

    Missing · 0/20

    Add a “Steps to reproduce” section with at least two numbered steps. Why this matters

  • Expected vs actual result

    Missing · 0/15

    Missing both expected and actual results. Why this matters

  • Environment details

    Partial · 5/10

    Some environment info found. Add build/version, browser or device, OS, and which environment (prod, staging). Why this matters

  • Evidence attached

    Missing · 0/15

    Attach a screenshot, console log, HAR file, or trace, and quote the exact error. Why this matters

  • Impact on users

    Missing · 0/5

    Say who is blocked and what it costs them: affected users, revenue or SLA risk, and any workaround. Why this matters

  • Severity and priority

    Missing · 0/5

    Set a severity (how bad: Blocker–Trivial) and a priority (how soon: P1–P4). Why this matters

  • Neutral, factual tone

    Missing · 0/10

    Blame language detected (“again”). Describe the behavior, not the people. Why this matters

  • Enough detail

    Missing · 0/5

    Only 23 words of real content. A reproducible report is rarely under 40.

  • No leaked secrets

    Pass · 5/5

    No passwords, tokens, or API keys detected.

How scoring works

Reproduction steps (20 points), expected vs actual (15), and evidence (15) carry the most weight because a report without them cannot be acted on. Title, environment, and tone are worth 10 each; impact on users, severity and priority, length, and secret detection are worth 5 each. A partial match earns half the points. The grader uses pattern matching, not AI, so treat it as a checklist, not a verdict.

Read the full guide: How to write high-quality bug reports.