About Centerpoint Connect

Centerpoint Connect is an all-in-one software platform built for commercial roofing contractors, covering CRM, project management, service dispatch, estimating, and client portals. The platform serves hundreds of roofing companies across North America, with a web application and native Android and iOS apps.

‍

The Challenge

Centerpoint Connect runs a focused engineering team, and delivering quality coverage across a platform this broad requires the right tools. Their senior QA engineer had built automated tests using Selenium and .NET, but like many teams scaling their automation practice, the existing approach had limitations around maintenance and CI integration with tests requiring ongoing upkeep and ran locally rather than as part of the release pipeline.

‍

"I want to try and catch as many things before our customers catch them and tell us about them," said Nate Selof, Lead Engineer at Centerpoint Connect. "It's worth investing the time and expense to do that."

‍

The team tested new releases and bug fixes thoroughly, but scaling a full regression pass across every module to match a faster release cadence required a smarter approach. They were shipping one release per week and pushing toward two, and needed a testing solution that could grow with them.

‍

The Solution

Centerpoint Connect adopted Docket to build a regression suite that covers their core platform flows without writing or maintaining automation code. Instead of hardcoding selectors, Docket navigates the UI visually using screen coordinates - the same way a human tester would. Tests are written in plain English, describing what to test rather than scripting how to test it.

‍

The switch from Selenium to Docket addressed the two challenges that had made automation difficult to scale. First, tests stopped breaking every time the UI changed. Docket's self-healing automatically adjusts when elements move (e.g. a button shifts down, a menu gets reorganized, a new banner appears) without anyone touching the test. Second, writing tests went from hours of .NET scripting to minutes of describing the flow in natural language.

‍

The team also valued that Docket wasn't limited to their QA engineer. Because tests are written in plain English, anyone on the team, including product managers, senior customer service reps, and trainers can create and understand tests without a technical background.

‍

For dynamic flows where content changes between runs such as different user lists, varying form states, new data, Docket's AI steps handle the unpredictability naturally. Rather than scripting exact values for every field, the AI reads the screen and makes contextual decisions, catching edge cases that rigid scripts would miss entirely.

‍

The Results

Centerpoint Connect now runs a comprehensive regression suite before every release. What previously required significant time from manual testing and Selenium maintenance now completes in under 30 minutes, giving the team confidence to ship faster without worrying about regressions slipping through.

‍

"Before Docket, regression testing required hours of constant upkeep," said Selof. "Now we run the full suite in under 30 minutes, and tests don't break with UI changes."

‍

The regression suite covers flows across the full platform - everything from lead capture and estimating through service dispatch, production tracking, and the client portal. Docket enabled Centerpoint Connect to expand their regression coverage to a full platform-wide suite, representing a fundamental shift in how they ship software.

‍

"Docket gave our team the confidence to ship faster without sacrificing quality. For a platform as broad as ours, reliable regression coverage isn't a nice-to-have - it's how we protect our customers." - Will Riley, CEO, Centerpoint Connect

‍

Docket makes Centerpoint Connect's QA engineers significantly more productive by providing a reliable automation layer, freeing them to focus their expertise on exploratory testing and complex edge cases instead of repetitive manual checks.

Key outcomes:

• Pre-release regression testing reduced from hours to under 30 minutes
• Full platform coverage across all major modules within weeks of onboarding
• Self-healing tests that survive UI changes without manual maintenance
• Plain English test authoring accessible to non-technical team members
• QA engineer's time freed up for higher-value exploratory work

‍

‍