The setup
The client's Maximo estate had been actively developed by the partner across major projects since 2018 — but testing hadn't kept pace. Stakeholders flagged it as lacking quality, structure and scope, with uncaught issues repeatedly reaching production. Then came the forcing event: a large restructuring of Maximo security and security groups, with predictable regression risk across the whole system.
The scale problem
The partner did the disciplined thing first: documented every business-critical area, ran workshops with the client's Maximo SMEs, and built a structured library of formal test cases.
Which created the next problem. A library that size, run manually on every release, would consume more tester hours than any release window could afford — the predictable end-state being incomplete testing exactly when deadlines were tightest.
Why MaxTAF
The partner evaluated the automation market — Maximo-specialised frameworks and generic tools both. Their cost-benefit analysis, weighing time-effectiveness against functionality, identified MaxTAF as the tool that could build robust tests inside the time that remained before the deadline.
The delivery
- 200+ test cases in 3 months — the MaxTAF test recorder plus its XML scripting language sustained an average of 3–4 automated cases per day, built from the manual scripts and system documentation already in hand.
- Visible as it was built — regular three-way progress meetings (client, Code Development, partner) meant the client watched the suite grow in real time rather than auditing it after the fact.
- Support that kept pace — a Premium Support SLA from Code Development resolved tooling questions as they arose, keeping project delay to a minimum.
The result
The client was left with a fully functional, documented automation suite — runnable on demand, schedulable on a regular cadence — and the ability to fully test business-critical areas of their Maximo without fear of uncaught regressions. Test coverage and testing productivity were transformed against where the engagement began.
What this engagement teaches
- Documentation first. A test regime starts from system documentation — and SME workshops are the fastest honest way to build it.
- Manual testing has a feasibility ceiling. Past a certain library size, the man-hours for full coverage stop being available. That's the automation trigger — not fashion.
- Speed of test development is the whole game under deadline. A recorder-led workflow let a time-pressured team deliver a large script library inside a window nobody believed was enough.
Facing a security restructure, an upgrade, or a regression pack that's outgrown your testers? Talk to us → — or if you're a delivery partner, this is exactly the kind of engagement you can embed in your bid.