How GreatLab tests every change
GreatLab builds the software dental labs run on: orders, invoices, scans, and connections to the tools labs use every day. We have worked together for over two years. They run Fire Your QA on every change they ship, and they have helped us immensely, from the very first version.
Over two years of working together
Fire Your QA was built inside our partnership with GreatLab. It was tested on their real work every day and shaped by their team's feedback, and it now runs on every change they ship.
July to October 2026
Taken from GreatLab's own systems on 10 October 2026.
1 in 3
changes where it found a problem (135 of 378 tickets tested)
284
bugs reported since 27 July 2026, each with screenshots and a video
85%
of its bugs were later confirmed by GreatLab's manual QA team
618
QA runs on real changes, and 771 reports published
About 480 hours of testing, done automatically
Those 618 runs carried out about 2,900 checks. Done by hand at around 10 minutes each to test and write up, that is about 480 hours, or 12 working weeks of a tester's time.
This is an estimate based on the number of checks, not a measured figure.
Testing the same 618 changes
The full setup
Every change tested
Each merge is picked up, tested on a private copy of the app with a fresh test account, and reported.
Reports where the team works
Full reports in Confluence, three evidence links on every Jira ticket, and a short summary in Slack.
Regression suites
118 test cases across orders, finances, settings and more, run 739 times since August.
Want to hear it from GreatLab?
Book a demo and ask about GreatLab on the call. We'll show you real reports from their work, then run Fire Your QA on your own app.
- Real reports from GreatLab's work
- A live run on your own app
- One clear price within two working days
Fire your QA backlog,
not your team
Let agents test every pull request, keep your regression suites green and send your team clear reports, videos and bug tickets.