Load Test Plug-ins are pre-compiled Java classes that can be loaded into the recorded web session to enhance the functionality of a load test program.
When a plug-in is used, it is automatically copied into the same directory where the load test program is stored (at the time when the load test program is saved). Before a load test can be executed the load test plug-in(s) (*.class) and the load test program (*.class) must be zipped together to one ZIP archive (similar like input files). All required load test plug-ins are automatically transmitted to the Exec Agent(s) when a load test is started.
Plug-in attributes:
File: the file-path of the plug-in.
Please note that the original source of all plug-ins is always the top-level 'Plugins' directory of the Project Navigator.
Plug-ins in all other directories are always duplicates of the original plug-in classes and will be updated/overwritten when the original plug-in is modified.
Last Modified: timestamp when the plug-in has been created or updated in the corresponding directory.
Plug-in Type: always fixed to ' Load Test Plug-in'.
Plug-in Name: the name of the plug-in which is shown in the GUI (Var Handler).
Construct Scope: the level on which the plug-in is initialized during the load test. Possible levels are 'global' (at the start or the end of a load test), 'per user' (at the start or the end of a user) or 'per loop' (at the start or the end of each loop). 'not fixed - arbitrary' means that the initialization level is arbitrary selectable in the GUI.
Execution Scope: the level on which the plug-in is executed during the load test. Possible levels are 'global' (at the start or the end of a load test), 'per user' (at the start or the end of a user), 'per loop' (at the start or the end of each loop), 'bound to URL' (before or after an specific URL call is executed) or 'bound to every URL' (bound to all URL calls - executed before or after every URL is executed). 'not fixed - arbitrary' means that the execution level is arbitrary selectable in the GUI.
Note 1: if a plug-in is bound to an URL call and the execution order is set to 'before', the output parameters of a plug-in can not be used to set CGI or Form input parameter of the same URL call because the context of the plug-in contains already all URL request data. In such a case you have to bind the plug-in to the preceding URL call, 'after' the preceding the URL call is executed.
Note 2: if the execution scope of a plug-in is defined as 'per loop' and the execution order is defined to 'after', the plug-in will not be executed if any URL call of the corresponding loop fails.
Execution Order: the order when the plug-in is executed (before or after the execution scope). not fixed - arbitrary means that the execution order is arbitrarily selectable in the GUI.
Allow Multiple Usage: defines if the plug-in can be used several times in the same load test program.
Input Parameter: list of plug-in input parameters (input variables). The column 'Name' shows the labels of the input variable names which are shown in the GUI. The column 'Utilization' shows if the input parameter is required or optionally selectable. The column 'Assign From' shows if a normal, existing variable must be used in the GUI or if a new User Input Field is automatically created when the plug-in is used.
Output Parameter: list of plug-in output parameters (output variables). The column 'Name' shows the labels of the output variable names which are shown in the GUI. The column 'Utilization' shows if the output parameter must be allocated to a variable, or if acquiring the plug-in output is optional. The column 'Extract To' is always fixed to [variable].
Plug-in Description: the description of the plug-in which is shown in the GUI.