The client
A European financial regulator running IBM Maximo (with ICD) in an environment where change control is unforgiving and the formal testing window is measured in hours per month — not weeks. Every release, patch and change ticket competes for the same sliver of validated time.
The road here — a failed first attempt
The team's first automation attempt used Selenium. It consumed a massive amount of effort and never produced a dependable suite — generic browser automation kept fighting Maximo's dynamic UI instead of working with it. The turn came on a recommendation: an independent Maximo consultant who had used MaxTAF elsewhere pointed the team at a tool built for Maximo rather than pointed at it.
The operation today
- ~200 automated cases run daily — a regression suite that executes routinely, not ceremonially, so drift is caught the day it happens rather than at the next release.
- New cases per release, on a budget — the team works to a target of around five new automated cases per release, shared out against support and change tickets, so coverage grows with the system instead of lagging it.
- Stability as the discipline — the team's stated first challenge is keeping scripts stable over months of system change; the recorder-plus-scripting workflow is what makes maintenance a routine task rather than a rebuild.
- Reporting upward — granular results feed summarised reporting the team can hand to management, so testing is visible as an assurance function, not a black box.
Why it matters
In most organisations a missed regression is an inconvenience. In a regulator's estate it's an incident. This operation shows what Maximo test automation looks like when it has to work inside real constraints: a narrow window, a small team, an unforgiving audience — running every day for years.
A pattern we see repeatedly across regulated engagements: the first Selenium attempt fails, a specialist recommends a Maximo-native tool, and the suite that results runs daily instead of quarterly.
Running Maximo somewhere failure isn't an option? Talk to us about your constraints →