Client stories
How Clarrio made testing part of building, not a handoff
Test coverage climbed from 30% to 75%, end-to-end tests that took 40 minutes now take under 10, and with testing no longer the bottleneck, releases roughly doubled with zero production incidents since.
The Challenge
Clarrio is a data aggregation and analytics platform that connects multiple sources of real-world and clinical data into a unified environment. The product ran on a Cypress suite maintained by a QA. It covered the critical flows, but every new test was slow to write and the suite got harder to keep passing as the product changed. Maintenance ate into real testing time, and the knowledge to do it sat with one person.
The Solution
With Thunders, Clarrio's team writes end-to-end tests in natural language and runs them straight away. Most of the rollout went into translating existing test logic, not learning a tool. The QA was working independently within three weeks, and features shipped as they were built, without waiting on a separate testing handoff.
Key results
30% → 75%
test coverage
40 min → under 10 min
to write one end-to-end test
2x
release frequency, with zero production incidents since adoption
Before Thunders
Cypress covered Clarrio's critical flows, but the setup came with a familiar cost. Writing new tests was slow, and keeping the suite passing as the product evolved took a real chunk of the team's testing time. The ability to write and maintain tests also sat with one QA, so quality depended on a single person rather than the whole team.
Implementation
The rollout was straightforward. Clarrio had tests running in the first week, and the QA was working independently after about three weeks. Most of that time went into translating existing test logic rather than learning the tool. The QA writes tests day to day. Because the tests read in plain language, the PM and Head of IT can review runs before a release themselves, which wasn't practical when everything was code. The bigger shift was cultural: testing stopped being something one person owned. Every member of the team now writes tests as part of shipping a feature, and adoption spread on its own. QA and engineers started using Thunders within the first couple of weeks, without anyone pushing them to.
It's the tool that made end-to-end testing feel like a normal part of building a feature, instead of a separate, painful step at the end.
Tayssir Cherif
Head of Development @ Clarrio
Result
In the first six weeks, Clarrio wrote around 120 tests and moved test coverage from roughly 30% to 75%. The average time to write one end-to-end test dropped from about 40 minutes to under 10. Thunders has caught regressions before they reached users, including a critical login bug. Since adoption, Clarrio has shipped with zero production incidents. With testing no longer the bottleneck before a release, the team ships more often, roughly double its previous rate, and is comfortable shipping later in the week than it used to be.
Ready to ship faster with smarter testing?
