Assetize

Automation Script Test Harness

Test an Automation Script before it reaches your Maximo.

Paste a launch point script, pick the release, and run it against a mocked Mbo right here. You get a graded verdict for each release: passes, breaks, or skipped where the release lacks an attribute the script reads.

Run a script now · Download the kit · Documentation

Run a script now

Start from an example or paste your own script. Run one scenario or the whole pack. Libraries, method results and related records sit with the scenario, so an autokey script or a script that calls another script runs here. The same runner opens inside Studio. JavaScript runs in this tab.

The same check, wherever you work

One engine grades every run, so the browser, your terminal and CI give the same verdict.

  • On your machine, before you commit: node bin/asz-harness.mjs script.js --lens mas92 — the one release you build against, like a unit test.
  • In CI, before you merge: node bin/asz-harness.mjs script.js --lens 761,mas811,mas90,mas91,mas92 — every release you support, as a gate. Set it up for operations.
  • From your AI tools, while you write: test_automation_script_evidence(source, lens) on the MCP server lists the attributes a WORKORDER script uses and whether each exists on a release.

Jython too: mvn verify -P mas91 or -P mas92 runs the full JUnit suite. For a whole version-aware Maximo in a browser terminal, open the test stub.

What a result looks like

Two Object launch point scripts from the kit (wo_costcentre.py, wo_costcentre.js) — WORKORDER, save, before save — run on MAS 9.1 and MAS 9.2. ZZ_SHIFT exists on MAS 9.2 only, so its case runs on 9.2 and is skipped on 9.1. A third script, wo_shift_unconditional.js, reads ZZ_SHIFT with no isNull() guard and blocks on both releases: a missing attribute on 9.1, service.error() on 9.2. That is the bug the harness is there to catch.

Each difference gets one of the three grades MXH gives a full upgrade assessment: BLOCKING, REVIEW or ENVIRONMENT. A release with no evidence for the script is marked NOT ASSESSED. Open a full sample report.

Every launch point type

  • Object — fires on save: add, update, delete, from the UI, the MIF and REST/OSLC.
  • Attribute — fires on initialize and validate for one attribute.
  • Action and Sig Option — fires when invoked: a button or a workflow step.
  • Cron task and escalation — fires on schedule, with no user in the loop.