AI can write your code. AI can suggest your test cases. But when it's release day — someone still has to run the tests. This template is for that person. A complete Google Sheets QA system for teams without a QA engineer: - Test Cases with dropdown menus - Bug Tracker with severity levels - Auto-calculated Dashboard with Go/No-Go status - Release Checklist — 17 checks before every launch $9 one-time. Includes Quick Start Guide PDF. Ready in 5 minutes.
No reviews yetBe the first to leave a review for QA Test Management System
Maker
📌
Hey Product Hunt 👋
AI tools are great. But for QA, someone still has to open the device and run the tests. I built this for that person.
I'm a QA engineer with 4+ years of experience. I built this because I kept seeing the same problem — small dev teams shipping bugs that a simple checklist would have caught.
No QA tool budget, no QA engineer, just a messy spreadsheet or nothing at all.
This template is my attempt to fix that. Would love any feedback from the community!
Report
A Sheets template is a smart move for teams that aren't ready for a full tool like TestRail. If I can suggest one thing, consider adding a way to link test cases directly to bug tracker rows so you can see which specific tests failed for each bug without cross-referencing manually. That connection is usually what kills me in spreadsheet-based QA setups once you get past a handful of releases.
Report
Maker
@cartoptimizer That's a great point, Aubrey! Linking test cases directly to bug tracker rows is on my roadmap for v2.0. For now, the Bug ID column in the Test Cases tab lets you reference manually — not ideal, but it works for smaller teams. Thanks for the feedback, it's exactly what I needed to hear!
Report
Maker
@cartoptimizer I just pushed v2.0 this morning with exactly that.
Bug ID in Test Cases now pulls the status directly from Bug Tracker, and Bug Tracker shows the linked TC result on the same row. No more manual cross-referencing.
Existing buyers get the update at no extra cost. Your feedback genuinely shaped this one, so thanks for taking the time to write it.
Hey Product Hunt 👋
AI tools are great. But for QA, someone still has to open the device and run the tests. I built this for that person.
I'm a QA engineer with 4+ years of experience. I built this because I kept seeing the same problem — small dev teams shipping bugs that a simple checklist would have caught.
No QA tool budget, no QA engineer, just a messy spreadsheet or nothing at all.
This template is my attempt to fix that. Would love any feedback from the community!
A Sheets template is a smart move for teams that aren't ready for a full tool like TestRail. If I can suggest one thing, consider adding a way to link test cases directly to bug tracker rows so you can see which specific tests failed for each bug without cross-referencing manually. That connection is usually what kills me in spreadsheet-based QA setups once you get past a handful of releases.
@cartoptimizer That's a great point, Aubrey! Linking test cases directly to bug tracker rows is on my roadmap for v2.0. For now, the Bug ID column in the Test Cases tab lets you reference manually — not ideal, but it works for smaller teams. Thanks for the feedback, it's exactly what I needed to hear!
@cartoptimizer I just pushed v2.0 this morning with exactly that.
Bug ID in Test Cases now pulls the status directly from Bug Tracker, and Bug Tracker shows the linked TC result on the same row. No more manual cross-referencing.
Existing buyers get the update at no extra cost. Your feedback genuinely shaped this one, so thanks for taking the time to write it.