mySAP Toolbag for Performance Tuning and Stress Testing

12.1. Repeatable, Repeatable, Repeatable!

Before I dive into test-run execution, discussion of a couple of high-level housekeeping items is in order. First and foremost, my mantra now and for the remainder of the testing and analysis stages is “consistency”—everything I do must be repeatable, predictable, and completely documented. If I make a change, regardless of how slight—to my test infrastructure, a script, a test package used to execute a script, the data, or even processes I will use in starting, ramping up, executing, monitoring, and ramping down my test run—I must carefully document this change. In a perfect world, close attention to test-run documentation would be unnecessary, because there would be no change to a test environment or ...