Skip to content
BENIBIX Learn

Bug Report

Development🧪 Testing & QualityTest Practices

Also known as Bug Ticket, Defect Report, Issue Report

A note that tells the team what broke and how to make it happen again.

Think of it like

Think of it like telling a doctor where it hurts. The clearer you are, the faster they can help.

Example

Lucy writes: add a mug, add coupon SAVE10, open the cart. She expected 18, but saw 21.60, in Chrome on Windows.

Why it matters

A bug nobody can repeat rarely gets fixed. Clear steps save hours of guessing.

Definition

A bug report tells the team about something that does not work. A good one has a short title and the exact steps to make the bug happen again. It says what you expected and what actually happened. It names the device, the browser and the app version. A screenshot or a log helps even more.
A good bug report has steps, expected, actual and where.

Common mistake

Writing it does not work. Without steps, the expected result and the actual one, nobody can help.

Key takeaways

  1. 1
    Steps to repeat. Exact steps, one at a time.
  2. 2
    Expected and actual. Say what should and did happen.
  3. 3
    Where it happened. Device, browser and version.