Bug Report Template
--- Copy this template ---
Title:
[Feature/Area] - Brief description of the issue
Severity:
Critical / Major / Minor / Cosmetic
Priority:
P0 (Blocker) / P1 (High) / P2 (Medium) / P3 (Low)
Environment:
- OS: [e.g., macOS 15.3, Windows 11, iOS 19]
- Browser: [e.g., Chrome 125, Safari 18.2]
- App Version: [e.g., v2.4.1, commit hash]
- Device: [e.g., MacBook Pro M3, iPhone 16]
Steps to Reproduce:
1. Go to [URL or starting point]
2. Click [specific element]
3. Enter [specific input]
4. Observe [what happens]
Expected Behavior:
[What should happen]
Actual Behavior:
[What actually happens]
Screenshots / Recordings:
[Attach relevant media]
Additional Context:
[Console errors, network logs, frequency of occurrence, workarounds]
Example Bug Report
[Checkout] - Discount code not applied when cart has 10+ items
Severity: Major
Priority: P1
Environment: Chrome 125 on macOS 15.3, Production (v2.4.1)
Steps to Reproduce:
- Add 10 or more items to the shopping cart
- Navigate to /checkout
- Enter discount code "SAVE20" in the promo field
- Click "Apply"
Expected: 20% discount applied to the order total.
Actual: Error message "Invalid code" appears. Discount is not applied. Works correctly with 9 or fewer items.
Console error: TypeError: Cannot read property 'length' of undefined at validateDiscount (checkout.js:142)
Tips for Writing Better Bug Reports
- One bug per report: Mixing multiple issues in a single report makes tracking and resolution harder. File separate reports for separate bugs.
- Be specific, not vague: "Checkout is broken" is unhelpful. "Discount codes fail when cart contains 10+ items" is actionable.
- Include what you tried: If you tested workarounds or variations, note them. This saves the developer from repeating your investigation.
- Attach visual evidence: A screenshot or recording is worth a thousand words. Show the error state, not just describe it.
- Note frequency: Is this 100% reproducible, intermittent, or a one-time occurrence? This dramatically affects how the developer approaches debugging.
Automating Bug Reports
Manual bug reports are only as good as the person writing them. Automated testing tools can generate comprehensive reports with perfect reproduction steps, exact browser and environment details, screenshots at the point of failure, and network/console logs — every time, consistently.
Bugster generates detailed bug reports automatically when its AI agents detect issues during end-to-end testing. Each report includes the exact steps that triggered the bug, the expected vs. actual behavior, and supporting evidence — no manual filing required.
