4 October 2026 Oussama Belakhdar 2 min read

Case study: regression testing cut from 10 days to 2 hours

A 14-month QA architect engagement for a French document digitisation company. A document processing platform that also carries healthcare flows (third-party payment, care claims, patient files), a web portal, APIs, and no automated tests at the start.

Key takeaways

Regression: from 10 days to 2 hours for a full campaign.
Releases: from once a month to once a week.
Starting point: zero automated tests. Cypress for the web portal, Postman for the APIs.
Everything runs in CI (Jenkins and GitLab CI), with traceability in Jira and Xray.

The context

A document digitisation and processing platform.
Sensitive healthcare flows: third-party payment, care claims, patient files.
A web portal and APIs exchanging data with third-party systems.
Fully manual acceptance testing: 10 days for a regression campaign, one release a month.

We name neither the company, nor the product, nor its clients.

What was put in place

A risk-based test strategy, starting with healthcare flows and document processing.
API tests with Postman on exchanges between systems.
Web portal tests with Cypress on critical journeys.
Traceability of requirements, tests and defects in Jira and Xray.
Automated execution in CI, with Jenkins and GitLab CI.

The results

Indicator	Before	After
Automated tests	none	Cypress + Postman, in CI
Regression campaign	10 days	2 hours
Release frequency	once a month	once a week

These results are the ones observed on this engagement. They depend on each project's context: this is not a promise for every project.

What we take away

Start with the APIs: for flows between systems, these tests are more stable and faster than UI tests.
Fictitious test data, never real health data.
Test rejections as much as successes: a rejected document must be explained and correctable.

And for your team?

If your acceptance testing still takes days, a QA audit gives you a clear picture: a written assessment, a test strategy and a costed action plan, in 5 days, for €1,000 excl. VAT as a fixed fee. Delivered remotely, in English or French. The first scoping session is free.

See the QA audit at €1,000 excl. VAT

Frequently asked questions

What did this engagement achieve?

A full regression campaign went from 10 days to 2 hours, and release frequency from once a month to once a week, over a 14-month engagement.

Which tools were used?

Cypress for the web portal, Postman for the APIs, Jira and Xray for test management, Jenkins and GitLab CI for automated execution.

Can healthcare flows be tested with real data?

No. Tests use fictitious data created for the purpose. Real health data has no place in a test environment.

How much does a QA audit cost at AutomationDataCamp?

The QA audit and diagnosis costs €1,000 excl. VAT as a fixed fee, over 5 days: a written assessment, a test strategy and a costed action plan. The first scoping session is free.

Engagement report by Oussama Belakhdar, QA architect. Company, product and end clients not named. Written with the help of AI; the figures are those reported by the author for this engagement.