LeadingReach Achieves Faster Releases and Enhanced Quality with mabl

Challenge
icon-bottleneck-white

LeadingReach was facing the challenge of code being produced faster than QA could test it, threatening their high quality of standards.

Outcomes
Icon_Runner

Defects in code detected 3x faster

icon-clock-white-1

35% decrease in time spent on manual regression

Icon_Web

40% increase in amount of test coverage

LeadingReach, a company that specializes in referral management & healthcare communication, found themselves facing the same challenge as many other highly technical SaaS products: balancing the need to meet a high standard of quality with the rapid pace of software innovation. When they made the decision to partner with mabl, they overcame many of these challenges and ultimately transformed a portion of their QA process.

  • Significant Reduction in Testing Time: LeadingReach saw a 35% decrease in the time spent on regression testing cycles, freeing up valuable QA resources.
  • Improved Bug Detection: mabl helped LeadingReach identify defects on average 3 days earlier in the development cycle, significantly reducing the cost and effort of fixes.
  • Increased Test Coverage: Test coverage expanded by 40%, leading to more comprehensive quality assurance and a more robust platform.
  • Reduced Rework for Developers: Developers spend less time fixing issues found late in the cycle, improving overall team efficiency.
  • Empowered QA Team: The QA team now spends more time on strategic testing and less on manual regression, elevating their role from gatekeepers to proactive partners.

 


The Challenge

LeadingReach recognized that consistent regression testing is fundamental to assuring a high quality product. “If our system isn’t working properly, there can be delays in patient care,” explains Jeremy Pfingsten, QA Manager. “If the quality is there, then we're not impacting anybody; we're making things faster and better for everybody. So it's really important that our system is working all the time and has minimal defects.” Requiring a low threshold for defects, LeadingReach built a comprehensive set of regression tests for their product lines. With each new release, the number of regression tests increased. Eventually, manual testing put product releases at risk of delay. Spending time building and automating tests written in Python or Cypress, could take days to write when testing needed to be done in hours.

Goals in Using mabl

From a leadership perspective, one of the most significant goals in using mabl was to automate repetitive regression testing, helping to accelerate release cycles and improve the overall quality and stability of releases. By reducing the risk of defects, expanding test coverage, and running tests more frequently, the QA team was empowered to strategically innovate and focus on higher-value activities.

Ultimately, leadership’s goals closely aligned with those of the QA team, who were looking for an easy to learn and maintain solution to eliminate the tedium in the manual testing process. They wanted to shift from execution and maintenance towards more strategic endeavors like test design and analysis, utilizing a tool that could quickly adapt to a product that is continually evolving.

Implementation

The decision to adopt mabl stemmed from a thorough evaluation of its capabilities, ease of adoption, and ability to seamlessly integrate with its existing workflows. The mabl team provided robust support in the rollout, ensuring LeadingReach’s development and quality initiatives were being met. mabl’s ongoing support is also a significant factor in how successful the implementation has been for the team, with Jeremy Pfingsten noting, “mabl support is amazing, but the better thing is that you don’t really need it that often because everything just works.”

The onboarding for the QA team was remarkably smooth, with the team quickly understanding how to create and maintain tests, implementing them earlier in the software development lifecycle than they have been able to in the past. There are multiple ways mabl made the implementation easier, such as the auto-healing capabilities that help to significantly decrease test maintenance times, and the robust educational training available through mabl University, which allowed testers to understand automation and begin creating tests.

Benefits: A Unified Leap in Efficiency and Quality

It didn’t take long for the impact of mabl to be realized for the LeadingReach team, including:

  • 90% reduction in manual tests, with plans to automate the remaining tests by end of year
  • Reduction in defects post-release requiring hot fix
  • Doubled the amount of test coverage
  • Boosted QA confidence in the quality of both the process and the product

The LeadingReach team noted several other benefits as well including the cost savings that come with not having to redo work and being able to optimize resource allocation within the QA team.

The team noticed impacts beyond the product itself, identifying potential issues much earlier in the development lifecycle, and dedicating more time to value-added activities like exploratory testing and new feature validation, leading to greater job satisfaction. They also noted the product is “fun to use,” a sentiment not often attributed to testing software. These feelings have generated significant buy-in from the entire company, not just the people who are involved in the day-to-day testing practices.

Conclusion

Leadership, management, and the QA team at LeadingReach now view mabl as an indispensable partner in their goals to balance innovation and quality. With enthusiasm for future quality initiatives and the desire to automate as much of their testing as possible, mabl is fundamental to their strategy for continued growth and delivering the best possible product to their clients.

Try mabl Free for 14 Days!

It’s the only SaaS solution that tightly integrates automated end-to-end testing into the entire development lifecycle.