Analyzing Terminal-Emulation Test Scripts

Once you have generated a test script you should determine if the script runs without error by performing a Try Script run. A Try Script run will determine if the script accurately recreates the recorded interactions.

The default option settings for Try Script runs include live display of data downloaded during the test run and the writing of log and report files.

With Try Script runs only a single virtual user is run and the stress test option is enabled so that there is no think-time delay between transactions.

  1. Click Try Script on the workflow bar. The Try Script dialog box opens.
  2. To view rendered page transitions during a Try Script run, check the Animated Run with TrueLog Explorer check box.
  3. Click Run.
    Note: You are not running an actual load test here, only a test run to see if your script requires debugging.

    The Try Script run begins. The Monitor window opens, giving you detailed information about the run’s progress.

    TrueLog Explorer opens, showing you the data that is actually downloaded during the Try Script run. Each main terminal emulation window accessed during recording is listed as a high-level WebTelnetRecvCommand API node in the menu tree.