How GoodShape's QA lead scaled testing for 20 developers — without growing the team
With a 10:1 developer-to-QA ratio and a newly hired QA lead, GoodShape needed to build test automation fast. Bugzy gave them nightly regression coverage and Jira-driven verification in weeks, not months.
“The tool became so independent — it picks up the Jira tickets ready for testing on its own and just reports the results in Slack. Every morning I see that the main test cases have passed, and I feel comfortable knowing the system is tested constantly.”
GoodShapeWith a 10:1 developer-to-QA ratio and a newly hired QA lead, GoodShape needed to build test automation fast. Bugzy gave them nightly regression coverage and Jira-driven verification in weeks, not months.
20 developers, 2 QAs, and a new automation mandate
GoodShape's engineering team had grown to 20 developers, but QA capacity hadn't kept pace. With only two QA engineers and a 10:1 developer-to-QA ratio, manual regression testing couldn't cover every release. The team hired a dedicated QA lead to build an automation practice from scratch — but standing up a test framework, writing hundreds of test cases, and integrating with their Jira-driven workflow would typically take 3-6 months before any real coverage existed. Meanwhile, releases kept shipping with limited verification.
“I really enjoy the fact that I can tell it what I want to happen and it just does it.”
Jira-driven verification by day, nightly regressions by night
GoodShape connected Bugzy to their Jira and Slack workflows within the first weeks. When developers move a Jira ticket to review, Bugzy automatically verifies the changes — generating targeted test cases and running them against the latest build. Every morning at 6 AM, a scheduled regression suite runs against the full application, and results land in Slack before the team's standup. The QA lead uses Bugzy to generate test cases from Jira ticket descriptions, building a growing regression suite without writing each test manually. Over five months, the system processed 133 Jira events automatically, generated 169 test case sets, and executed 598 test runs — all with an average cycle time under 12 minutes. The workflow is 70% event-driven, meaning testing happens as a natural part of development, not as a separate phase.
1,000 test runs, two critical bugs caught, and releases shipped with confidence
In five months, GoodShape ran over 1,000 automated test executions with a 97% success rate. Early on, Bugzy caught an unexpected security issue where a user with an invalid password could log into the system due to a session-handling bug — the kind of vulnerability that manual testing might miss entirely. More recently, it flagged a CSS pointer-events issue in a modal backdrop that blocked users from accessing a core system feature when automation was involved. The nightly regression suite catches issues before the team arrives each morning, and since the beginning of 2026 the team ships releases with more confidence, knowing release tasks are covered and tested through constantly running scheduled runs.
| Metric | Before | After |
|---|---|---|
| Regression testing | Manual, before major releases only | Automated nightly + on every Jira ticket |
| Test case creation | Manual authoring (weeks of work) | AI-generated from Jira tickets |
| Time to QA results | Hours to days | < 12 minutes average |
| QA coverage model | Reactive — test what you can | Proactive — everything verified automatically |
What's next
GoodShape plans to expand Bugzy coverage to additional projects and teams, deepening the Jira integration to verify more ticket types and extending their nightly regression suite as the product grows.