Overview
Last updated
Last updated
testgrinder automates Maximo by interacting with it just like a human would - solely through the Maximo UI (user interface) by moving the mouse, clicking buttons, entering field values, etc. - by following the steps in scenarios you provide and reporting the outcome in a run report complete with screenshots and video. It is great for:
Data management
Initial data load
Data updates
Data cleansing
Data verification
Training
Generate annotated training videos
Regenerate training videos on change easily
Share recorded training videos
Configuration management
Consistent change deployment
Accelerated change deployment
You write testgrinder scenarios in steps that sound like natural language, which makes the scenarios easy to follow by anyone familiar with Maximo. As an example, here's a scenario that creates a new Maximo asset and changes its status to ACTIVE:
Once you kick off a run, you may watch it execute in real time. As scenarios execute, testgrinder compiles a run report including screenshots for every step as well as a video for each of the scenarios. You may share a run report with others if you choose to do so. Here's the run report for the above scenario:
As testgrinder executes a run, it will employ several tgBots, each running one scenario at a time. This allows scenarios to run in parallel, greatly reducing the total runtime. For example, a run with about 200 scenarios, totaling over 6,000 steps, being executed on 50 tgBots will take about ten minutes to complete. For comparison, if such a task were to be done manually in Maximo, it would require dozens of man-hours.