How Space42 went from manual regression to 60% automated coverage in four months.

The challenge: A handful of testers against a 40-developer org, and no cloud tool allowed.

Space42’s QA team worked closely with developers and product, validating each new feature and running a manual regression cycle before every release.

As the platform grew, every new feature and workflow added another set of checks to the regression cycle. The suite became increasingly difficult to execute manually within a two-week sprint, with approximately three testers supporting a 40-developer organisation.

Space42’s on-premise environment is not allowed to call any external URL. Any automation solution therefore had to run entirely inside their own secure infrastructure.

The application itself added another layer of complexity. Analysts zoom and pan a live map, draw polygons over satellite imagery, work with geospatial data, and push large files through ingestion. These workflows required more than straightforward UI recording and demanded a carefully designed automation approach.

Why Testsigma: Automation that runs on their infrastructure, building a collaborative QA capability

Space42 deployed Testsigma on-premise, on its own infrastructure. Test data, application data, and execution all stay within their network.

Devendra Singh Josan, Lead Engineer, Testing, set the direction. He came up with the automation strategy and coordinated the effort.

Mark Angelo Casuco took the build. He came from code-level automation, so he knew what the script-driven route costs in framework upkeep and locator maintenance, and he built a significant portion of the automation suite on that experience.

Chandrasekar, from the wider functional testing team, supplied the part automation engineers usually have to guess at. He walked Mark through the application's manual workflows, business scenarios, and functional behaviour, which turned the suite into meaningful scenarios rather than a recording of individual UI actions.

The team also addressed some of the application’s most challenging interactions rather than excluding them from automation. Platform-specific capabilities were developed to support complex map interactions, including polygon drawing and geolocation, turning previously difficult manual scenarios into reusable automated steps.

The result: From manual regression to 60% automated in just over four months.

• Approximately 60% of current platform scope is now covered by automation, including key modules and critical workflows that previously required significant manual regression effort.
• The team moved from a predominantly manual regression approach to automated coverage of the highest-value workflows in just over four months, without slowing down ongoing releases.
• Regression execution can run in parallel, providing faster feedback and allowing QA engineers to spend more time on new features, exploratory testing, and edge cases.

Testsigma has enabled us to scale automation within our secure on-premise environment while significantly improving regression efficiency and coverage of critical GIQ workflows. Beyond automation, it has strengthened our quality engineering capability, delivering faster feedback, greater release confidence, and a more scalable approach to testing.

Devendra Singh Josan

Lead Engineer – Testing, Space42

It also produced a more collaborative automation model. Testing leadership, automation engineering, and functional domain knowledge now work the same problem together, which is what let coverage expand while the team kept supporting live releases.

What’s next

The next marker is 90% automation coverage of the platform’s relevant workflows. The plan remains focused on improving stability, expanding meaningful coverage, and moving more automated execution into the delivery pipeline so that testing becomes an integral part of the software delivery process rather than a step performed only after development.