A Sample IxLoad TestComposer Workflow
The following is a sample operations sequence used for creating, editing, persisting, and executing a TestComposer script:
Configure global script parameters as described in Defining Script Properties.
Start adding script steps as described in Adding Scrips Steps, which covers the addition of command using multiple supported approaches, such as using the Step Configuration wizard or using the plug-in's Capture functionality.
Detailed reference information for all supported steps is given in Script Steps Reference Information.
A script can have associated parameters, which can be assigned specific values when the script is run as a custom test from the IxLoad QuickTests configuration page. Specifying such script parameters is described in Defining Input Parameters.
For any TestComposer script you can define user events that possibly occur at script execution time and configure the response to such events. See Defining User Events.
Results of Execute-type steps can be retrieved in order to be further evaluated in subsequent steps and determine the script execution flow. Retrieving user-defined portions of step results is done using Response Templates, as described in Retrieving Step Results using Response Templates.
The values of script variables can be specified as statistics to be exported at script execution time. See Specifying Exported Statistics.
A TestComposer script can have an associated pass/fail expression, which defines whether the script executed successfully or not. Defining a script pass/fail expression is described in Specifying a Script Pass/Fail Result.
Eventually, after having finished the editing operations, in order for the script to be saved, it has to be validated first, as described in Validating a Script.
The most simple mode of persisting a script is saving it into the IxLoad configuration that contains it. See Saving a Script into an IxLoad Test Configuration. Alternatively, a script can be saved as a procedure resource for re-use across different scripts, as described in Creating Procedure Resources.
Complex debugging features, such as the use of breakpoints that halt the script execution at user-defined locations and permit the inspection of the runtime parameters in those occurrences, can be used while in the plugin's Debug mode. See Executing a Script in Debug Mode.
After having been edited and debugged, a script can be run from any IxLoad context, or as a custom test from the IxLoad QuickTests configuration page, as described in Execution from the IxLoad GUI.
Eventually, a script can be exported to Test Conductor for further editing and execution in an automated manner.
IxLoad TestComposer │ User Guide |