I built QA Bug → Regression Test because I kept seeing the same gap in software testing workflows: finding and reproducing a bug is only part of the job. After that, QA engineers still need to document the issue clearly and often create a regression test manually. I wanted to connect those steps. The extension records browser actions such as clicks, fills, navigation and assertions, then turns that session into a structured Playwright regression test. It also tries to improve the generated output by using stable locator strategies, removing redundant actions, masking sensitive values and warning about weak locators. My goal is not to replace Playwright Codegen. The goal is to reduce the repetitive work between reproducing a bug and turning it into a regression test. I’m especially interested in feedback from QA engineers, software testers and automation engineers: Would this fit into your current workflow, and what would you want the tool to generate or improve next?

QA Bug → Regression Test

Turn recorded bugs into Playwright regression tests

Turn recorded bugs into Playwright regression tests