Client stories

How Infopro Digital’s QA manager stopped guessing what was automated

From unreadable scripts to a team that writes its own tests, in plain language, without engineers in the loop.

The Challenge

Automation was a black box, even for the QA manager. Manual and automation QA teams worked in silos. Tests started as manual cases that were then translated into Java, and the QA manager had no visibility into what was actually covered. A separate tool was needed just to bridge code and humans. Slow, opaque, and hard to scale.

The Solution

Tests anyone can write, read, and own. Thunders replaced the code-first model with tests that read like sentences, not code, giving the QA manager full visibility and control over every test. No Java, no middleware, no translation layer.

Key results

~100 tests

built by the QA team itself, no automation engineers required

Product Owners

starting to automate their own user stories from the build phase, removing the QA bottleneck

QA expanded

from a specialist function to a cross-team practice

Before Thunders

Two teams, one tool in the middle, and no visibility. Infopro Digital runs complex B2B data and media products. Their QA process ran on a split model: manual testers wrote the test cases, automation engineers translated them into Java. The pipeline worked slowly. And it left a critical gap: the QA manager couldn't read the code, so she had no way to check whether the automation actually matched what the manual team had specified. To get better visibility, the team added a third layer, just to connect the automation to something human-readable. Every test involved three handoffs before it was done. The overhead was real, and the process didn't scale. Meanwhile, AI was changing everything around QA. Hanen saw it clearly: if AI was reshaping development and every other function, testing couldn't stay frozen in place.

Implementation

Starting with the hard problems first. One of the first challenges they tackled with Thunders was automating graphical pages, reading stamps on documents, extracting dates, and identifying who signed. Tests that classical automation simply couldn't do, Thunders handled them. The rollout started with testers and the QA manager, then began expanding to product owners. The goal from the start was structural: get POs writing tests for their own user stories, directly from the build phase, without waiting for the QA team to pick it up downstream.

It's a revolution for QA. It's a testing culture, not just a tool.

Hanen Khalfaoui

QA Manager @Infopro Digital

Result

A team that automates on its own, and a new definition of QA. The team built around 100 tests on their own in a few months, without hand-holding. That alone was the big surprise. Tests that would have taken weeks to write were live quickly, and they went further than classical tests ever had. The bigger shift is cultural. QA at Infopro Digital is no longer a function that sits at the end of the pipeline. It's becoming something the whole product team participates in, managers, testers, and product owners, all working in the same tool, in the same language. For Hanen, that's the point. Thunders changes who testing belongs to.

Trusted by

Microsoft logoOrange logo
LegalPlace logoUptale logo
Medius logoSopra Steria logo
Cegid logoPwC logo
Allianz logoInfopro Digital logo
Axeptio logoIncorta logo
SNCF Connect logoBNP Paribas logo
Microsoft logoOrange logoLegalPlace logoUptale logoMedius logoSopra Steria logoCegid logoPwC logoAllianz logoInfopro Digital logoAxeptio logoIncorta logoSNCF Connect logoBNP Paribas logo
Microsoft logoMedius logoAllianz logoSNCF Connect logo
Orange logoSopra Steria logoInfopro Digital logoBNP Paribas logo
LegalPlace logoCegid logoAxeptio logoCegid logo
Incorta logoPwC logoUptale logoPwC logo

Frequently Asked Questions

How did Infopro Digital replace its 3-layer, code-first QA process?

By replacing three separate automation layers and code-first scripts with natural language tests. The QA team now writes tests that anyone can read and own, without relying on automation engineers to translate them.

Can non-engineers write and own automated tests with Thunders?

Yes. Because tests are written in natural language, Product Owners and QA specialists at Infopro Digital built and now maintain around 100 tests themselves, without writing any code.

What are natural language tests?

They are tests described in everyday language instead of code, so the whole team can read and edit them. At Infopro Digital, that turned QA from a specialist function into a shared testing culture.

How quickly can a QA team get up and running with Thunders?

Within a few months, Infopro Digital’s team built around 100 tests on their own, including complex cases that were previously manual, such as reading stamps, dates and signatories on documents.

Ready to ship faster with smarter testing?

Screenshot of the Thunders app Test Cases list, showing test sets, labels and last run status, with a label picker open