The problem
As a QA engineer, I was spending 20-30 minutes on every single bug report.
Write the steps. Attach the screenshot. Record the video. Explain the environment.
Jump on a call because the developer "can't reproduce it."
Sound familiar?
What I built
I built Bug Reproduction Recorder — a Chrome extension that automates the
whole thing.
Here's the flow:
- Click Record
- Reproduce the bug
- Click Stop
- Get a fully structured bug report — automatically
The report includes:
- Video recording of the session
- Screenshots captured at key moments
- Browser info, OS, page URL
- Reproduction steps
- Shareable public link
Why I built it myself
I looked at existing tools — Jam, BrowserStack Bug Capture, Loom — but they were
either too expensive for solo QA engineers, too heavy, or required the whole team
to sign up.
I wanted something lightweight, free to start, and focused purely on bug
reproduction.
Tech stack
- Chrome Extension (Manifest V3)
- Supabase (auth + storage)
- Google OAuth
- Vanilla JS
Try it
🔗 Chrome Web Store: https://chromewebstore.google.com/detail/bug-reproduction-recorder/bjljppfeefaemnnilkbigfmegaaebkmd
🌐 Landing page: https://bugrecorder-landing.vercel.app
It's free to start (20 reports/month). Would love your feedback — especially
from fellow QA engineers. What would make this 10x more useful for you?
Top comments (0)