Define general test settings

Where do I find it?

To set the general load test settings:

  1. Open the Load Tests tab.
  2. Choose an existing test.
  3. Click the General button.

Back to top

Basic settings

In the Basic settings, you provide a name and description for your test that will enable you to identify at a later time.

Action How to
Test name

Specify a meaningful name for the test. The test name cannot exceed 140 characters. To enable test duplication, ensure that the name does not exceed 120 characters.

Description Add a description of your load test.
Email a report when the test finishes

Select the checkbox to send a report by email when the load test finishes. By default, the report is sent to the logged in user, but you can add up to another five email addresses by clicking + Add emails.

Back to top

Run configurations settings

In the Run configurations section, you choose a license mode, run mode, and other run-related settings.

Action Description
License mode

Indicates the license type to use:

  • VUH. Enables you to run Vusers by the hour in load tests. 1 VUH is effectively 1 Vuser executing a load test for 1 hour.

  • VU. A fixed license enabling you to run Vusers.

  • Mixed VU/VUH. Uses VU licenses first and when no more are available, then uses VUH licenses to reach the required number of Vusers.

Run mode

Sets the run mode type:

  • Duration. The load test will run each script for as many iterations as possible in the script's configured time duration. This is the default option.

  • Iterations. The load test will run each script for the number of iterations configured for the script.

    Note: You also configure a maximum duration for a script. If the number of iterations configured for the script has not been reached within this time, the Vusers for the script are terminated. The following features do not support the Iterations run mode:

    • Adding Vusers
    • Manual and advanced scheduling for scripts
    • Generating single user performance data
    • The Timeline tab when scheduling a load test
    • Changing the load in a running load test that is configured for iterations
    • DevWeb scripts included in a load test configured for Iterations mode that is run on an on-premises load generator, are only supported on on-premises load generators version 2020.05 or later.

  • Goal Oriented. The load test will run until a configured threshold is reached. For details, see Configure a goal for a load test.

Pause scheduling

Pauses the scheduling during a test run.

Select the total possible pause time during a run from the dropdown list (the maximum is two hours).


  • This feature does not support the Goal Oriented run mode.

  • When pausing is enabled, the following features are not supported:

    • Adding Vusers
    • Single user performance
    • Changing the load when running a test

For details on pausing a schedule during a run, see Pause scheduling during a test run.

Add Vusers

Allows you to increase the number of Vusers while your test is running. When you enable this setting, you also need to provide a non-zero value in the Scripts page, indicating the number of Vusers. For details, see Configure the script schedule.

Note: This feature is only relevant for Duration mode.

Caution: To cover the cost of initializing extra load generators, additional VUH charges will apply.

Delayed start

Delays the start of the test run, after initialization, for up to 60 minutes.

This options adds 1 VUH to each Vuser in your test.

Exclude think time from TRT calculation

Excludes think time from the results and report calculations for the transaction response time. The load test's status bar, the Dashboard, and the Report indicate whether think time was excluded from the run. By default, this option is disabled, and think time is included.

Excluding the think time may affect the result's trend and benchmark comparisons if this option was not enabled for the compared run.

Note: To use this feature when running Vusers on an on-premises load generator, version 2020.10 or higher of the on-premises load generator is required.

Group transactions

Creates a transaction group for all the transactions with the same name in all scripts included in the load test. Metrics for this transaction group are displayed in the Dashboard and in Reports, in addition to the metrics for the individual transactions.


  • This option does not support dynamic transactions.
  • Transaction groups are not included in raw transaction data for export. For details on storing raw transaction data, see Store transactions raw data.
Optimal percentile (T-Digest)

Instructs LoadRunner Cloud to use an optimal algorithm based on T-Digest in the Report, when calculating the percentile for TRT (transaction response time). For details, see Report sections.

This option is enabled by default. If you disable it, LoadRunner Cloud will use an average percentile algorithm. For details, see Percentiles.

Back to top

Data and logs

Set the data and logging preferences.

Action How to
Stream script errors to Splunk

Enables the streaming of script errors to a Splunk account. For details, see Stream script errors to Splunk.

Note: When this option is disabled, even if the check box is selected, errors will not be streamed to Splunk.

Store script errors

Stores all script error messages generated during a test run, in raw format.

For details of exporting this data, see Export raw script error data.

Note: This option is not supported for on-premises load generators earlier than version 3.5.

Store transactions raw data

Stores transaction data generated during a test run, in raw format.

For details of exporting this data, see Export raw transaction data.

Note: Transaction groups are not included. For details on grouping transactions, see Group transactions.

Collect Vuser logs from cloud-based load generators

Collects Vuser logs from the cloud-based load generators used in the load test.

For details on downloading the logs, see Run results options.

Note: Collecting Vuser logs may cause the load test to take longer to stop after it has run.

Collect Vuser logs from on-premises load generators

Collects Vuser logs from on-premises load generators used in the load test.


For details on downloading the logs, see Run results options.

Note: Collecting Vuser logs may cause the load test to take longer to stop after it has run.

Back to top

Load generator settings

You can add scripts from your assets and then manage them as follows.

Action How to

Enable multiple IPs from cloud and on-premises load generators

Enables multiple IP addresses on each load generator.

This option is applicable for load generators in an AWS cloud (all regions excluding China) and for Windows on-premises load generators.

IP addresses are assigned to Vusers on a round-robin basis. For example, if a load generator has 10 IP addresses and 100 Vusers are running on it, the first 10 users will each have a unique IP address and subsequently, each group of 10 Vusers will repeat the IP address pattern.

Supported for the following script types:

  • Mobile Application HTTP

  • SAP Web
  • Web HTTP

  • Web Services

Note: Scripts in which WinInet is enabled do not support multiple IP addresses.

For details, or to enable this feature, contact your account manager or sales representative.

On-premises load generators (Windows)

For Windows on-premises load generators, you must ensure that you have assigned all the valid IP addresses to the load generator machine so that LoadRunner Cloud can use them in the load test.

Cloud-based load generators (AWS)

For AWS cloud-based load generators, LoadRunner Cloud will automatically assign a maximum of 15 IP addresses for a single load generator, with a maximum of 300 IP addresses for the entire load test. To modify these default values, open a support ticket.

When using the default values, LoadRunner Cloud:

  1. Determines the required number of cloud-based load generators required for the test.

  2. Configures 15 IP addressees on each cloud-based load generator (or less, if applicable).

  3. Fails the test if the total amount of required IP addresses that need to be set for the test exceeds 300 (the default maximum).

  4. Fails the test if there are not enough allocated IP addresses to be distributed among the cloud-based load generators. This applies when you have dedicated (allocated) IP addresses for cloud-based load generators. The IP addresses used for the test will only be taken from the allocated IP address pool.

The following examples show the different IP requirements for a test configured to use 1,000 TruClient Vusers and based on a limit of 25 Vusers for each cloud-based load generator (thereby requiring 40 load generators for the test):

Do not use allocated dedicated IPs for load generators on the cloud

If dedicated IP addresses were assigned to your tenant, by default LoadRunner Cloud only uses cloud-based load generators on the dedicated IPs. To use cloud-based load generators on a non-dedicated IP for a specific test, disable this option.

For details, see Dedicated IP addresses.

Enable script assignment to selected on-premises load generators

Select this check box if you want to assign scripts in a load test to be run on specific on-premises load generators. For details, see Scripts.

Permit use of Linux load generators for Web Vuser scripts

LoadRunner Cloud will try to use Linux cloud load generators (where applicable) to run Web Vuser scripts, providing faster provisioning.

To enable this feature, open a support ticket.


  • This applies only to Web HTTP Vuser scripts.

  • Scripts in the load test cannot include Windows dependencies (such as a path or DLL).

  • Client side breakdown and network emulation are not supported.

  • Data Format Extensions (DFEs) are not supported. For details on DFEs, see the VuGen Help Center (select the relevant version).

Use Private VPC Enabling this option lets you use a private VPC during a test run, for the specific region for which it was configured. For details, see Load test with a dedicated VPC.

Back to top

See also: