Customers
What changes when tests stop breaking.
As a startup, our earliest and best feedback comes from a handful of design-partner teams using Nerro Labs against real production UIs.
Series B fintech · Checkout platform
30% → 2%
Flaky test rate
A 25-person engineering team was losing roughly a day a week to test maintenance — locators breaking on routine CSS changes, failures nobody trusted enough to block a release on. Within a month of switching their checkout suite to visual AI comparison, flaky failures dropped from 3 in 10 runs to roughly 1 in 50.
“We cut our flaky test rate from 30% to under 2% in the first month. QA finally trusts the pipeline again.”
QA Lead, design-partner team
B2C marketplace · 40-person engineering org
~1 day
Saved per sprint
Self-healing locators meant the team stopped filing a recurring ticket for 'update test selectors after redesign.' Over a two-week sprint, that time went back into writing new tests instead of repairing old ones.
“Self-healing tests saved us roughly a day of maintenance every sprint. That's a day back for actual testing.”
Staff Engineer, design-partner team
Open-source design system maintainers
200+
Components covered
A small maintainer team needed regression coverage across every component variant without hand-writing assertions for each one. Visual baselines across Storybook stories gave them that coverage in an afternoon, with new components picked up automatically as they're added.
“We went from spot-checking components by eye before a release to full visual coverage we don't have to think about.”
Core maintainer, open-source project
Want to be the next story?
We're onboarding a small number of design-partner teams directly with the founders.