RecBeamPart of Bug reporting
Reset to a clean state, say what you expect, reproduce the bug once, say what happened, stop, and share a link to the moment it breaks.
Prepare
- Get to a known starting state: logged in, right account, right page.
- Close unrelated tabs and turn on Do Not Disturb so notifications do not appear in the recording.
- Note the environment: browser version, operating system, app version.
Record
- Share the tab where the bug happens, not your whole screen. See how to screen record in Chrome.
- Turn on your microphone.
- Perform the steps slowly enough to follow.
- Stop as soon as the bug has appeared.
What to say
Speak the structure of a bug report: "I expect X. I do A, then B. Instead Y happens." Say any error message aloud. This gives the developer expected versus actual results in your own words.
Share it
Attach the link to the ticket and note the timestamp where it breaks. Trim long takes with the free video trimmer if you saved a file.
With RecBeam
Choose Bug Report mode before you start. After you record, RecBeam transcribes it, drafts the title, numbered steps, acceptance criteria and a suggested severity, and files it to GitHub or Linear with a link to the failure moment (Business + AI plan). You review before anything is filed. Compare the written result with the structure in how to write a bug report, or see bug report examples.
Questions
How long should a bug report video be?
As short as possible while still showing the steps. Link to the moment the bug appears so nobody has to watch the whole video.
Do I still need written steps?
Yes. Video shows the failure and written steps make it searchable and easy to repeat. RecBeam drafts both.
Is a screenshot enough?
For a visual glitch, yes. For anything that takes several steps, record.