Customer Use Case

BNP Paribas Cardif uses Leapwork to automate testing for its insurance policy management system

  • Web Web
  • Desktop Desktop
  • Banking and Finance-1 Insurance
Automation type
  • Regression Testing Regression testing


Key Results

  • From quarterly to monthly releases 
  • An average of 10 minutes to automate a test 
  • Test execution time down to 2 minutes per case


As a world leader in the creditor insurance market, it is essential to deliver tailored options to the right customers, quickly.

BNP Paribas Cardif rely on hundreds of distribution partners to provide products and services across a variety of sectors, from banking and automotive to retail and telecoms. To do this, their partners use BNP Paribas Cardif’s web-based partner portal to access the organization’s policy management system, developed by Pegasystems.

“Everything in our organization is in one way or another connected to this system”

Johan Stolk, Senior Test Engineer

The availability and quality of these applications is therefore critical. However, as regression testing requirements grew, they QA team struggled to keep up with the mounting workload. This hindered time to market and increased the likelihood of critical errors entering production.


With Leapwork, BNP Paribas Cardif have been able to transition to an agile approach, running the regression suite automatically at 3 stages in the delivery pipeline. Testers don't need to upskill to write tests with Selenium or spend hours performing manual checks. In this way, testing time has been dramatically reduced, the speed of delivery has increased three-fold, and the QA team can focus on more exploratory work.

“We could automate the testing of all our core business applications by spending two dedicated months”
Johan Stolk, Senior Test Engineer



Download the whitepaper: How no-code test automation drives agile transformation

Get an overview of Leapwork as a test automation solution for the BFSI industry. Includes: 

  • QA challenges and the Leapwork solution
  • Key Leapwork features
  • The impact of a no-code approach