Execution As a Custom Test
Any procedure script (both the Main_Procedure and other scripts) that is contained in an IxLoad test configuration can also be run as a custom test from the QuickTests configuration page of IxLoad. If the executed procedure has input parameters defined, this execution mode supports the passing of values to the input parameters.
When run as a custom test, all runtime information from the TestComposerDebug mode is available.
To run a TestComposer script as a custom test:
Go to the IxLoad QuickTests configuration page. In the Home ribbon click thebutton to create a new QuickTest.
In the QuickTest window that appears, select a test. In the subsequent Test Items page, which lists all procedures defined in the current IxLoad configuration, select a procedure to execute by clicking its associatedcontrol.
In the Finish page assign a name to the QuickTest to be created. When completing this operation, a new QuickTest is created and becomes selected in the list of defined QuickTests. Click thebutton to launch the script execution.
After completing the script execution, detailed runtime information is displayed in the IxLoad Data Miner page, as described in Script Execution Results Integration in Data Miner.
Execution from an IxLoad Tcl API Script
A TestComposer test script can also be run from an IxLoad Tcl API script.
For running a TestComposer test, you need to create a new IxLoad QuickTest of the User Defined Test type that `wraps' the Composer test, then use the ixNet exec start <test_reference> API command to launch the test.
Example:
Given a QuickTest referenced in the IxLoad configuration by the /quickTest/eventScheduler[1] string, you can use the following Tcl API commands to launch it into execution and wait for it to finish:
Set testID {/quickTest/eventScheduler[1]}
ixNet exec start $testID
ixNet exec waitForTest $testID
IxLoad TestComposer │ User Guide |