How Lucra Automated 70% of Regression in Hours
How Michael Schmidt, CTO of Lucra, replaced months of traditional test scripting with natural language automation and fundamentally changed how his team approaches QA.
By Yuvan Sundrani · August 2025 · 5 min read
What Lucra does
Lucra is a white-label social competition platform that powers gamified experiences for brands like Dave & Buster's, Five Iron Golf, Puttshack, and TouchTunes. Its SDK embeds peer-to-peer tournaments, challenges, and loyalty-driven contests directly into partner platforms, with Lucra handling payments, compliance, and risk management.
When your technology is embedded inside other companies' products, quality is not optional. A regression in the SDK does not just affect Lucra. It affects every partner running it.
The testing problem
Lucra's regression suite included over 250 manual test steps. Each full run required one to two hours of effort. For a team of roughly 30 people, that manual cycle consumed significant engineering and QA capacity on every release.
Traditional UI test scripting was the obvious alternative, but the economics did not work. Setting up meaningful coverage required months, and maintaining the resulting scripts consumed nearly a full-time engineer. Every UI change risked breaking tests unrelated to the change itself, creating overhead that scaled with the size of the suite.
Michael Schmidt, Lucra's CTO, has over 15 years of experience in mobile development.
With over 15 years in mobile development, I've seen firsthand how painful and time-consuming UI testing can be, especially for end-to-end flows.
What changed with Autosana
In under 15 hours of total effort, Lucra automated approximately 70% of their 250-step regression suite using Autosana's natural language test flows. Traditional UI scripting would have required months of setup to reach equivalent coverage.
We were able to automate the majority of our regression suite in a matter of hours instead of weeks or months, and the self-healing capabilities mean we spend far less time maintaining brittle tests.
Three factors drove the speed of adoption:
Natural language test authoring. Engineers describe what they want to test in plain English rather than writing element-specific scripts. No framework to learn, no selectors to identify, no test infrastructure to maintain.
Self-healing architecture. When the UI changes, Autosana's agent adapts without requiring test modifications. This eliminates the brittleness that makes traditional UI test suites expensive to maintain over time.
Overnight regression cycles. Automated test suites now run overnight. The QA team focuses on feature validation and bug identification during working hours rather than executing manual regression steps.
Results
| Metric | Before Autosana | With Autosana |
|---|---|---|
| Regression suite | 250+ manual steps, 1 to 2 hours per run | 70% automated via natural language |
| Time to reach automation coverage | Months (traditional scripting) | Under 15 hours |
| Test maintenance cost | Nearly a full-time engineer | Minimal (self-healing) |
| QA team focus | Executing manual regression | Feature validation and bug identification |
Why it matters for Lucra's business
Lucra's technology runs inside other companies' products. A bug in the SDK is a bug in a partner's app. The cost of a regression reaching production is not just a poor user experience for Lucra. It is a reliability issue for every brand running Lucra's white-label platform.
Automated overnight regression with self-healing coverage means Lucra can ship updates with confidence that partner experiences remain stable. As the company continues to expand across hospitality, entertainment, and media, that confidence scales with the business.
Autosana is the first solution I've used that makes robust, automated UI testing truly accessible. It's saved our team countless hours already and fundamentally changed how we approach QA.
Get started
Get started at autosana.ai.
Prefer a walkthrough first? Book a demo.