mySAP Toolbag for Performance Tuning and Stress Testing

12.6. Winding Down Test Runs

Once eTimer, another timing mechanism, or a closely watched clock indicates that the majority of my test run is nearing completion, it's time to begin thinking about winding down or “ramping down” the test run. This is necessary because most of the time I set up test runs to execute indefinitely (for flexibility in where I later mark the start and stop times for that particular run) rather than for a set period of time or a specific number of loops. Note that I set up this ability to run indefinitely at the script level (through a logic-controlled perpetual loop) rather than at the controller level, because it lets me run the same script standalone or as a scenario/member within a larger package. A number of methods ...