@DavidT

In Pega Robot Studio 19.1, the Pega Inspector let you set global variables at runtime to test different automation paths without changing the code. In version 22.1, that exact tool isn’t available, but you can achieve similar testing by using breakpoints and the Locals/Watch window in debug mode. When you hit a breakpoint, you can manually edit the values of global variables or parameters in the Watch window before continuing execution, which simulates the old Inspector behavior. Another option is to temporarily store test values in a configuration file or Excel sheet and load them at runtime so you can swap them easily without touching the main automation logic. For more complex scenarios, you can also create a dedicated “test harness” automation that initializes globals with different values and then triggers the automation under test. This allows repeatable tests without altering production code. While it’s not as direct as the old Inspector, combining debug tools, variable watches, and test harness automations gives you the same flexibility for unit testing in 22.1.

@DavidT In 22.1 and R25, testing of each automation has been made available instead of running the entire solution and then triggering each automation. Since each automation is best designed to be stand-alone, global variables would violate that principle. A best practice would be to limit the use of global variables and pass their values into and out of your individual automations that use them. There isn't a real way to test an individual automation and then alter a global variable to get it to respond to it. You could use a breakpoint and then the debug window to update the value, however this is artificial and is not operating at the speed you would see at runtime. My suggestion would be to pass your global variable value in and out of the automation as needed. This would allow you to test each automation individually as well as create unit tests to handle all the possible variations of your inputs and outputs.