📝Every QA engineer and developer knows the drill:
You find a bug. You manually write down steps to reproduce, take screenshots, and format a ticket for Jira or GitHub. Then, you open your IDE and write the exact same steps all over again in code for your automated regression suite.
Why do the same work twice?
I built QA Bug → Regression Test to bridge the gap between manual reporting and automated regression testing. 🎯
💡 How It Works:
Record the Issue: Click Start Bug Session in your browser and reproduce the bug naturally. Clicks, inputs, navigation, and timing are recorded cleanly.
Capture Inline Assertions: Highlight the visible error message, banner, or missing element right on the page to insert an immediate assertion.
Instant Dual Output:
🐞 Markdown Bug Report: Clean, formatted steps to reproduce with environment details and evidence, ready for GitHub Issues, Jira, or Linear.
⚡ Playwright Test (.spec.ts): Production-ready code using resilient locators (getByRole, getByLabel, getByText) that drops straight into your test repository.
🔒 Built for Privacy & Real-World QA:
Zero-Leak Redaction: Passwords, API keys, and session tokens are automatically detected and replaced with REPLACE_WITH_TEST_VALUE in code and [REDACTED] in reports.
100% Local & Offline-First: Manifest V3 compliant. Zero external tracking or servers—everything runs entirely inside your browser.
🔗 Chrome Web Store: https://chromewebstore.google.com/detail/qa-bug-→-regression-test/khoelciicbkdeieibchdndccdncpelbg?authuser=1&hl=tr
🎬 Quick Demo (YouTube): https://www.youtube.com/watch?v=GrtotYTfhbg
I’d love to hear your feedback on how this fits into your daily QA/developer workflow! Try it out and let me know your thoughts below! 👇