How Leasepath cut regression from weeks to hours, automated 51 critical tests, with near-zero maintenance.

Customer Overview

Leasepath is a modern, cloud-native platform that transforms equipment and asset finance operations, built on Microsoft Dynamics 365 and the Power Platform. By unifying CRM, origination, and post-booking workflows, Leasepath helps lenders accelerate deal flow, automate manual tasks, strengthen compliance, and deliver exceptional customer experiences. Organizations that use Leasepath streamline collaboration across sales, credit, and operations while gaining real-time visibility into pipelines and portfolio performance.

Find out what they were able to accomplish with testRigor.

The Problem

Leasepath had roughly 200 test cases documented in Azure DevOps, but none were automated. Regression testing required heavy manual effort—often pulling in QAs, BAs, and implementation consultants (up to ~15 people) for a week or more, and in some cycles stretching toward two weeks per release. This slowed releases, increased coordination overhead, and drained capacity from higher-value work like feature validation and customer-facing tasks.

They evaluated multiple scripting/recording tools (including Selenium), but flakiness and constant script maintenance kept undermining progress. Limited QA budget made it impractical to hire and retain automation engineers, so coverage stalled at 40%. At the same time, the product kept evolving on Microsoft Dynamics 365, where frequent UI changes from Microsoft further amplified the maintenance burden.

What Leasepath Wanted

• Increase the Regression Cycle’s Speed: Leasepath’s core app runs on Microsoft Dynamics 365. Before testRigor, regression required 1-2 weeks and up to 15 people across QA, BAs, and implementation consultants. They needed it fully automated so runs could complete in hours and be scheduled twice daily without developer involvement.
• Increase the Test Creation Speed: Prior to testRigor, Leasepath had zero automated tests despite around 200 documented cases. Traditional code-based tools slowed authoring. With testRigor, non-technical QA analysts can create tests in plain English; they’ve already automated around 51 priority tests with a huge number of steps and are accelerating toward broader coverage.
• Minimum Maintenance Effort: Existing scripts elsewhere were fragile and time-consuming to maintain. Leasepath needed low maintenance and reliable automation that withstands Dynamics UI changes. testRigor’s stable approach, detailed logs/timings, one-click PDF reports, and Azure DevOps/Teams integrations cut maintenance and find issues early, often catching upstream Microsoft changes before release.

Key Objectives

• Increase test automation coverage
• Test automation with manual QA
• Reduce test maintenance effort
• Achieve faster regression execution cycles
• Lower defect escape rate

"We don't need a software engineer to write the test cases to maintain them, which is the biggest pain point for everyone."

LEANDRO SANTOS SENIOR QA LEAD - LEASEPATH

The Solution

Leasepath considered multiple test automation tools and then selected testRigor as their automation platform to address the problems of slow regression, a lack of automation engineers, and a limited QA budget. Five QA analysts with no programming background now create, execute, and maintain automated tests entirely in plain English using testRigor. By running automated regression tests twice daily, the team reduced its test cycle from a two-week effort, which involved 15 people to approximately five hours. With regression testing fully automated, developers, business analysts, and consultants were freed from repetitive manual testing tasks. This allowed them to focus on innovation, feature development, and improving customer experience instead of routine validation.

The QA team successfully automated 51 of the most critical test cases covering core Microsoft Dynamics 365 workflows. Expansion is ongoing toward automating all 200 documented cases, ensuring end-to-end functional coverage and stronger release confidence. By leveraging Azure DevOps integration, every run automatically updates test case results, while Microsoft Teams integration provides instant notifications to the team.

Test maintenance has been reduced to a few quick updates after each run, keeping the suite efficient and up to date without consuming significant QA time. The QA lead described the impact of automation as a “godsend” for the team — citing major efficiency gains, reduced testing fatigue, and a smoother, faster release cycle.

Solution Highlights

• Non-technical QA analysts began automating tests instantly in plain English
• Automated 51 critical Microsoft Dynamics 365 test cases quickly
• Test run time reduced from two weeks to less than five hours
• Regression testing frequency increased from 2 weeks to twice daily
• New QA hires onboard fast, with minimal training and maintenance required
• Developers, business analysts, and consultants were freed from executing repetitive manual testing tasks

The Result

Leasepath achieved outstanding results by reducing regression testing from two weeks with 15 people to just ~5 hours automated, twice daily. This shift saved months of manual effort per release, freeing developers, BAs, and consultants from regression duties and enabling them to focus on higher-value work.

With testRigor, the team built 51 automated tests covering their most critical workflows and is steadily expanding coverage to all 200 documented cases. Importantly, non-technical QA analysts are now creating and maintaining these tests in plain English, eliminating the need for automation engineers and ensuring long-term scalability.

Summary

testRigor can also help you

testRigor’s generative-AI-based no-code automation platform makes it easy for QA teams to quickly build test automation while spending almost no time maintaining tests for web, mobile, desktop, databases, APIs, and mainframe apps. The tests are written in plain English, empowering anyone, regardless of their technical knowledge, to quickly build and maintain tests and understand test coverage.

This dramatically reduces the dependency on engineering resources, freeing developers to focus on building features. As a result, organizations can achieve faster release cycles with higher confidence in product quality.