Full throttle

One of the major enhancements delivered in this release of Testimony is what is called “Full Throttle”. Due to issues with the performance of the playback in previous releases, this option is now shipped with Testimony and is set to the default.

Previously, the master playback algorithm would attempt to ensure that all steps were played back in exactly the same sequence. However, the vast majority of transactions are independent of each other and can be identified with the “Dynamic ID” capability of Testimony.

This “time based sequencing” algorithm caused sometimes extremely long run times during playback and has thus been left available where the speed of playback is not critical.

It is recommended that you run the playback simulation program to obtain an estimate on the speed of playback and in this program you can choose the playback method to run the simulation for.

This option is configured via the general parameter “SEQ_STRATEGY”.

Sequencing strategy configuration

*The default configuration for the sequencing strategy is to use “Full throttle” as per the screen-shot shown above.

One of the biggest observations you will make with full throttle is that the bots will be almost constantly doing something. For example, SAP GUI transactions will be constantly executing from one screen to the next.

*An exception to this is that batch jobs will still be executed in the same sequence from the recording. These other types of transactions (batch jobs, RFC’s etc) will not be immediately visible from the output logs of the bots but will be visible in the monitoring section under “recently executed steps”.