Runtime settings let you fine-tune your scripts' and Vusers' behavior during test runs.
Runtime settings control the behavior of Vusers executing scripts generated by VuGen and other script generation tools. They include pacing, logging options, and think time.
The Runtime settings dialog box lets you view and edit the runtime settings that apply to your script and Vusers.
To access the runtime settings, select a script in the Assets > Scripts tab and click the Runtime Settings button .
Runtime settings nodes
The following table lists the nodes available in the Runtime settings dialog box.
Only runtime settings that are relevant to the selected script type are displayed and may be configured.
|Additional Attributes||Provide additional arguments for a Vuser script. Using this view, you can pass external parameters to existing scripts.|
Configure the browser, user agent, and proxy server connection settings for the script.
|Browser Emulation||Configure the user agent and simulate browser cache for browser related runtime settings.|
|Download Filters||Set the download filters for a script. You can filter addresses by a URL, host, or host suffix (TruClient).|
|HTTP||Configure HTTP connection settings.|
|JMS Advanced||Set the JMS advanced runtime settings for Web Services scripts. For more information, see JMS Transport Overview below.|
|Log||Configure the amount and type of information to be recorded in the log. You can download the logs after the test run.|
Configure miscellaneous settings for:
|Mobile Device||Change mobile device properties.|
|MQTT||Change MQTT runtime settings.|
Control the time between iterations. The pace tells the Vuser how long to wait between iterations of your actions.
You can control pacing either from the Load test > Script tab or Runtime settings > Pacing view. To select which setting is applied during run time, toggle the Local pacing check box in the script's settings in the Load test > Script tab.
|Preferences||Set various internet-related runtime settings.|
Configure the proxy sever connection settings.
Note: Proxy settings are ignored by cloud-based load generators.
|Replay||Configure replay settings, such as timeouts and user simulation. For DevWeb scripts, you specify when to create replay snapshots: Never or On error (Always is not supported in LoadRunner Cloud).|
Set the run logic runtime settings for a script. You can:
Note: Run Logic settings are not copied when you copy runtime settings from one script to another.
|SSL||Configure SSL connection settings.|
|Think time||Configure the think time settings, controlling the time that a script run waits between steps. These settings are designed to help you emulate a real user.|
Once you set the runtime settings for a specific script, you can copy them to other scripts of the same protocol.
To copy runtime settings and apply them to other scripts:
In the Assets > Scripts tab, select the script whose runtime settings you want to copy.
Click the Copy runtime settings button . The Select target scripts dialog opens with all scripts of the same protocol.
Select the scripts to which you want to apply the runtime settings, and click Apply.
Note: This feature is not supported for all protocols.
JMS is a J2EE standard for sending messages of either text or Java objects, between Java clients.
JMS implements Peer-to-Peer (also known as Point-to-Point) communication by defining a message queue as the target for a message. Multiple senders send messages to a message queue, and the receiver gets the message from the queue.
LoadRunner Cloud supports point-to-point communication by allowing you to send and receive JMS messages to and from a queue.
Before you can send messages over JMS transport, you need to configure the following settings that describe the transport. You configure these settings in the Runtime Settings > JMS Advanced view for a script.
|Use external VM||Enables you to select a different VM. If this option is not selected, Vusers use the JVM provided with LoadRunner Cloud.|
|Classpath||Specifies the Java classpath (vendor implementation of JMS classes).|
|Additional VM Parameters||Specifies extra parameters to send to the JVM, such as –Xms or –Xbootclasspath.|
|JNDI initial context factory||The fully qualified class name of the factory class that will create an initial context.|
|JNDI provider URL||The URL of the machine running the JNDI service.|
|JMS connection factory||The JNDI name of the JMS connection factory. You can only specify one connection factory per script.|
|JMS security principal||Identity of principal (e.g. the user) for the authentication scheme.|
|JMS security credentials||Principal’s credentials for the authentication scheme.|
|Number of JMS connections per process||The number of connections to create for each mdrv process. All Vusers sharing a connection will receive the same messages. Fewer connections results in better performance. Default=1, maximum=50 Vusers. Allowed values range is 1 – 50.|
|Received message timeout options||Select an option: Infinite wait – wait as long as required for the message before continuing. No wait – do not wait for the message, and return control to the script immediately. If there is no message in the queue, the operation fails. Specify timeout – use defined value. If no message arrives by the timeout, the operation fails.|
|User defined timeout||Specify the number of seconds to wait for the message before timing out.|
|Automatically generate selector||Select the checkbox if you want LoadRunner Cloud to automatically generate a selector for the response message with the correlation ID of the request.|