RecBeamPart of Bug reporting
A good bug report has a specific title, the environment, numbered steps, expected versus actual results, frequency and severity, and evidence such as a recording.
What every example does
- The title names the area and the problem.
- The environment is stated, so nobody guesses.
- Steps are numbered and each is one action.
- Expected and actual results are written separately.
- Evidence is attached or linked.
Use the template in our bug report guide as the skeleton.
Visual bug
Title: [Pricing] Annual toggle label overlaps price on narrow screens
Environment: Chrome 129, Windows 11, 360px wide window
Steps: 1. Open /pricing. 2. Resize to 360px. 3. Switch to Annual.
Expected: label and price on separate lines.
Actual: "Billed annually" overlaps the price.
Frequency: always. Severity: minor.
Evidence: annotated screenshot.A screenshot with an arrow is enough here. See the screenshot tool.
Functional bug
Title: [Checkout] Promo code SAVE10 removes shipping line, total shows $0.00
Environment: Chrome 129, macOS 14, logged-in customer
Steps: 1. Add an item. 2. Go to checkout. 3. Apply SAVE10.
Expected: 10% off, shipping stays.
Actual: shipping disappears, total is $0.00.
Frequency: 3 of 3. Severity: major (orders cannot be completed).
Evidence: recording linked at 0:42.Performance bug
Title: [Reports] Export to CSV takes over 60 seconds for 50k rows
Environment: Chrome 129, Windows 11, 16 GB RAM, office network
Steps: 1. Open Reports. 2. Filter last 12 months. 3. Click Export CSV.
Expected: download starts within a few seconds.
Actual: spinner for about a minute, then download.
Frequency: every time above ~30k rows. Severity: major.
Evidence: recording with a visible timer.Intermittent crash
Title: [Editor] Page crashes when pasting an image right after saving
Environment: Chrome 129, macOS 14, extensions disabled
Steps: 1. Edit a document. 2. Press Save. 3. Paste an image within 2 seconds.
Expected: image is inserted.
Actual: tab shows "Aw, Snap".
Frequency: 3 of 10 tries, only when pasting quickly. Severity: critical.
Evidence: recording of one occurrence, console error attached.Note how the frequency line and the trigger detail do the work. Record the failure with RecBeam's Bug Report mode and the written report is drafted for you. See also how to record a bug report video.
Questions
What should a bug report include?
A specific title, environment, numbered steps to reproduce, expected and actual results, frequency, severity and evidence. The full list is in how to write a bug report.
How do I report a bug that only happens sometimes?
Say how often it happened (for example 3 of 10 tries), what was different when it did, and attach a recording of an occurrence.
Are these examples real?
They are illustrative examples written to show structure.