A bug report often says “this button broke,” but the steps that caused it get lost. I built QA Bug → Regression Test to capture one manual bug reproduction and turn it into two editable starting points: a Markdown bug report and a Playwright TypeScript regression-test draft.
The workflow is straightforward:
- Open a web page and start a bug session from the Chrome side panel. The extension requests access to that site when recording begins.
- Reproduce the issue. The recorder captures supported clicks, form input, selections, and navigation. You can add visible-text or visible-element assertions, a bug title, expected and actual results, and one optional screenshot.
- Stop the session, review what was captured, then generate and download the report and test draft.
The goal is to reduce the work between finding a bug and writing down enough detail for someone else to reproduce it. The generated test is a draft, not a passing test guarantee: check its locators, warnings, skipped steps, and assertions, replace any test-data placeholders, and run it in your own Playwright project. The recorder currently focuses on the initial site's main frame; cross-origin pages and some popup or new-tab flows can need manual work.
Sessions are stored locally in Chrome. There is no account or cloud sync in this version. Recognized sensitive form values and supported URL query/hash values receive rule-based redaction, but detection is not exhaustive. Page text, URL paths, and screenshot pixels can still contain private information, so review every output before sharing it. The optional feedback form sends only the message and optional reply email you choose to submit; it does not attach your recording or screenshot.
The interface and bug reports support English and Turkish. The generated Playwright code uses TypeScript.
Try it: QA Bug → Regression Test on the Chrome Web Store
If you do manual QA or write Playwright tests, I'd be interested to hear which part of the bug-to-test handoff costs you the most time.
Top comments (0)