Defining Script Properties

The first step to configuring a TestComposer is script is defining the general script parameters, such as name, an associated runtime report level, and possible actions to take when predefined system events occur at script runtime.

To define the script parameters:

  1. Right-click a QuickTest tab header and choose the Properties command from the context menu that appears.
  2. In the Properties window specify a script name and an optional description for reference purposes.
  3. Define the script parameters as described in Table:Global Script Parameters:

     

    Table:Global Script Parameters

    Parameter
    Description

    Stop execution after <hh:mm:ss>

    Specifies a time interval after which the script execution is stopped unconditionally.

    Execute in real time mode

    A step that has been created in direct interaction with a configured device could possibly have a user delay, i.e. the user might first open a session and wait some time before inputting subsequent session commands.

    When this option is selected, scripts that are run as part of an IxLoad test ignore the user delay.

    Report level

    When run as an custom test from IxLoad, script run report information can be accessed from the IxLoad Data Miner page, as described in Script Execution Results Integration in Data Miner. The report information level is based on the following settings:

    • None: No report information is displayed.
    • Test Summary: Script-level summary information, such as start and completion time, number of steps, pass / fail condition, is displayed.
    • Step Summary: Each executed step is listed in the report. Steps that are part of any loop are listed multiple times.
    • Detail: Each executed step is listed in the report, with step information including the step response.

    In case of large responses, the information is truncated and you are referred to inspect the summary log.

    To end test use

    Defines whether an Abort (graceful termination) or a Stop (forceful termination) is used to end the test. when a timeout condition is encountered.

  4. Before actually starting to define a test script, you may want to configure additional Tcl packages to be used by the test, or configure global test-level conditional processing, as described in Tcl Packages and Events.