Interactive tool

The Perfect Bug Report.

A clear bug report gets fixed today. A vague one bounces back with questions and stalls for a week. Fill in the fields and this scores your report against what reviewers actually look for, then hands you a clean copy for Jira, GitHub or Slack. Your draft saves in your browser, and nothing you type leaves it.

Start from a template

1 · Identify

2 · Reproduce

3 · Evidence & impact

0%strength
Start filling in the report

    Live preview

    Practice after your draft

    Inspect the screen, find the bugs, then compare the report.

    After you understand the report format, practice like a tester: scan the product screen, tap the report-worthy defects, collect evidence notes, then load the completed sample into the builder.

    0/3 bugs found
    Checkout

    Field guide

    What separates a report that gets fixed

    Severity ≠ Priority

    Severity is impact: how badly it breaks the product. Priority is urgency, meaning what order it gets fixed in. A typo on the homepage is low severity but high priority; a crash in a yearly admin export is high severity but low priority. State both.

    The title formula

    [Area] what happens + where + under what condition. “Checkout button does nothing when the cart has 10+ items” gets read. “Checkout broken” gets bounced back with questions.

    One bug per report

    Two issues in one ticket means one gets forgotten and the other can’t be closed. Split them. Each report should be independently verifiable and independently closeable.

    Make it reproducible

    Start from a known state, one action per line, and include the exact data you used. Then say how often it happens. "Always" and "1 in 20" send a developer down completely different paths.

    Part of the loop

    A bug report is one step of three

    Before: run the tests

    Execute a run in the Test Run Simulator. When a case fails, it sends you here with the report half written.

    After: triage the defect

    Once it is filed, drive it through its lifecycle on the Defect Triage board: severity, priority, retest, closed.

    The full course

    Test Execution & Defect Management (Part 4) ties the whole loop together, from a fresh build to a go or no-go call.