Change Testing

testgrinder service will be discontinued on January 31, 2025

Every Maximo deployment goes through multiple changes over the course of its life. These changes could be simple reconfigurations or something more elaborate like adding a workflow process to support a business task or customization.

It goes without saying that each change needs to be tested before it goes live. Depending on your organization, this may be as simple as ad hoc testing or something more elaborate through a formalized process.

As each change is developed, you will write one or more testgrinder scenarios to test it with. Since it is very simple to rerun a set of scenarios in testgrinder, it is often a good idea for the change developer to write the test scenarios as well, rather than wait until the change gets to the individual responsible for testing it. Having the test scenarios developed alongside the change will be of value to the developer. With a click of a button, they can get almost immediate feedback on whether or not the change is working as they iterate upon the change. You may even consider tasking the functional analyst with drafting the scenarios as part of defining the change requirement. This will not only give the developer a starting point for the test scenarios, but also convey a clear vision of how the functional analyst sees the change work in the system.

As test scenarios for individual changes accumulate over time, you will build your test suite. At any point in time, you may rerun the entire test suite to confirm that all changes you've made to your Maximo so far are still operating as expected.