WHAT'S NEW · 01 AI TESTER
Build a test once with AI, then run it as MXML
There have been two ways to automate a Maximo test. Script it by hand and it runs the same way every night for next to nothing, but someone has to write it and keep it working. Describe it to an AI and anyone can create it in minutes, but every run costs money and no two runs take quite the same route. In 2.8.0 you describe the test once, the AI runs it, and MaxTAF hands back an ordinary MXML case. From then on it is a classical test.
01 WHAT IT IS
One AI run in. One MXML case out.
The AI tester reads a test written in plain English and carries it out against a live Maximo instance. What is new in 2.8.0 is what you are left with afterwards. While the AI works, MaxTAF records what it actually did and writes it out as MXML — the same Maximo-specialised language your other cases are already written in. The result is an ordinary MaxTAF case in your project.
Illustrative
02 WHY WE BUILT IT
Recording gives you both.
Classical automation earns its keep at scale. A scripted case is deterministic, the same steps in the same order every night, and running it costs next to nothing. The price is paid up front: someone with the skill has to write it, and someone has to keep it working as Maximo changes.
AI authoring turns that round. Anyone who can describe a test can create one, in minutes, with no scripting skill and little to maintain. But the AI does the work again on every run, so each run costs money, and an intelligent tester can take a slightly different route each night.
The intelligence is spent once, when the test is built. What runs every night afterwards is an ordinary script.
| Classical scripting | AI authoring | 2.8.0: AI-authored, MXML-run | |
|---|---|---|---|
| Effort to create | High: scripting skill, locators, page objects | Minutes, in plain English | Minutes, in plain English |
| Cost per run | Near zero | AI cost on every run | Near zero |
| Deterministic | Yes | Not guaranteed | Yes |
| Runs unattended at scale | Yes | Costly | Yes |
| Maintenance | Manual, ongoing | Low | Edit the MXML, or re-run the AI to regenerate |
03 WHAT IT MEANS FOR YOU
Deterministic and cheap to run. Minutes to write.
Deterministic
The same steps in the same order every night. When a run goes red, Maximo changed, not the route the AI took.
Cost-effective at scale
The replay uses no AI, so your AI spend does not grow with how often you run the suite.
Low effort to create
Written in plain English by whoever knows the process. No scripting skill, no locator hunting.
Low maintenance
A readable MXML case your team can edit a line of, or regenerate by running the AI case again when the screen changes.
04 GETTING STARTED
Up and running in four steps.
- STEP 01
Ask us to switch recording on
Ask us to switch recording on for your project. It is a project parameter we set for you — a few minutes, and no change needed on your side.
- STEP 02
Write an AI case
Write an AI case as you normally would and run it against Maximo.
- STEP 03
Find the generated case
Find the generated case in your Workspace. It is named after the run that produced it.
- STEP 04
Read it, then press Compile once
After that it runs like any other case, on demand or on a schedule.
A generated case arrives uncompiled — use Compile from the case options menu before the first run.
Editing and saving a case does not compile it.
Each AI run creates a new case rather than overwriting the last — keep the one you have reviewed.