Configuration management

testgrinder service will be discontinued on January 31, 2025

Often, Maximo configuration is done by hand, but sometimes changes get large and unwieldy. Say, for example, you are configuring a new external system with several enterprise services and publish channels. The amount of steps required to fully configure it may number into the hundreds. Rather than making these changes by hand, it is a good idea to script them in testgrinder. This will enable consistent deployment of the change as it progresses from Development, to Test, and Production environments. And the deployment runs will provide step by step documentation for how the change was applied with screenshots and video.

Your change management process may require developers to produce one set of testgrinder scenarios for deployment of the change, and another set for testing the change. The former is used to deploy the change and then retired, while the latter get added to the test suite and continue to be executed in perpetuity as part of ongoing regression testing.