background image
<< Selecting a diagnostic during recording | Viewing the Playback Results >>
<< Selecting a diagnostic during recording | Viewing the Playback Results >>
Visual C applications
Playing Back GUI Scripts
9-14
For Visual C/C++ and Visual Basic applications, the instrumentation added by
these tools causes the application-under-test to run considerably slower than the
uninstrumented program. For Java applications, the event monitoring causes
the application to run slower than usual. If you select Set timeout multiplier
value, Robot compensates for this effect by multiplying wait state values for
windows, wait state values for verification points, and delay values (between
user action and verification point commands, and between keystrokes) by the
specified value. If you need to fine-tune the wait states and delays further, see
Setting Wait State and Delay Options on page 9-6.
Set timeout multiplier value is not used if the application is not run under a
diagnostic tool.
3. If you selected any of the log check boxes in step 2c, click the Log tab and select
both Log management check boxes.
If Output playback results to log is cleared, the diagnostic tool opens (instead
of the log) after you play back the script. (For more information about the log
options, see Setting Log Options for Playback on page 9-5.)
4. Click OK or change other options.
You are now ready to play back the script. Keep in mind that the script will run
slower than usual because of the instrumentation or event monitoring added by
these tools.
NOTE: If a diagnostic tool was selected when the application was started
during recording, that tool overrides the tool selected in the GUI Playback
Options dialog box.