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 @InfoproDigital
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.
Ready to ship faster with smarter testing?
