Huenei cuts regression testing time 60% and gets its QA team off script maintenance.

The challenge: Every release was a bet on hope, not proof.

Huenei builds software for other companies. When something breaks after a release, the client feels it before Huenei does.

Keeping that from happening should have been straightforward. It wasn’t. Every UI change meant reopening the test scripts and fixing them one by one, manually. Tests ran scattered across environments and devices, with no single view of what had actually been tested. Releases shipped on hope more than proof.

The result: regression cycles that dragged, releases that slipped, and defects that reached the client’s hands instead of getting caught first.

"Before using Testsigma, our main challenge was the amount of time and effort required to maintain automated test scripts," said María Alejandra Ochoa, Software Engineering Director at Huenei. "Every UI change meant updating multiple scripts manually, which slowed down our regression cycles and increased the risk of defects reaching production."

Why Testsigma: How Huenei scaled QA without adding headcount.

Huenei evaluated other automation tools before choosing Testsigma. The deciding factor wasn’t a single feature. It was whether the team could move faster without adding headcount. With low-code test creation, engineers and non-technical QA staff started building and maintaining tests together. The team stopped funneling every change through the one or two people who knew how to write script. They brought web and mobile testing under one roof instead of running three separate ones. They ran tests in parallel and cut the clock time on every regression cycle. And they wired defects and coverage gaps straight into Jira, the workflow they already lived in, instead of a spreadsheet on the side.

Huenei now runs test creation and execution right inside its Azure DevOps pipelines. Testing lives inside the delivery process, not bolted on after the fact.

The result: From hope to release confidence.

Regression execution time down 60%. Five hours of combined manual and automated validation is now under two hours.

Test maintenance effort down 40%. Script updates that used to eat a QA engineer’s afternoon now take a fraction of that, because nobody’s updating the same test manually every sprint.

Automated test coverage up 35%. More of the application gets validated on every run. Issues surface before a client ever sees them.

"Since we started using Testsigma, we have significantly improved the speed and reliability of our testing process. This has also helped our development team receive faster feedback, reducing bottlenecks and improving overall delivery efficiency."

María Alejandra Ochoa,

Software Engineering Director, Huenei

The metrics are the proof. The bigger shift is what Ochoa’s job looks like now.

"My role is to ensure quality while keeping delivery timelines efficient. Testsigma has become a key part of that process by helping us scale automation faster, reduce maintenance effort, and improve collaboration across the team. It allows us to focus less on repetitive test execution and more on building a stronger quality strategy."