Define a load test

You add and configure scripts, monitors, and SLAs to a load test definition.

Where do I find it?

To create a load test, perform one of the following steps:

  • Select Load Tests >
  • Select Home page >

Back to top

Get started

From you Home page, you can select a project or create and edit a test.

Action How to

Select a project

On the Home page, select a project from the menu bar.

Create a test

To create a test, perform one of the following steps:

  • On the Home page, click .
  • On the Load Tests page, click .
Edit a test
  • Highlight a test in the grid.
  • Click Edit or click the test name link in the test grid.
Duplicate a test Click Duplicate to copy a test definition to a new test.

Back to top

Set general test settings

Create or edit a test from the Load Tests page.

Action How to
Test name

Specify the test name.

Description Add a description of your load test.
Email report

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 email.

This option is enabled by default.

License mode

Select a license type.

  • 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

Select 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 script types do not support the Iteration run mode:

      Gatling, JMeter, LeanFT, Selenium, TruApi, TruWeb

    • The following features do not support the Iteration 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.

  • Goal Oriented

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

Add Vusers

Enable adding Vusers during a test run.

Note: This feature does not support the Iteration run mode.

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

Delayed start

Select to delay the test run, after initialization, for up to 60 minutes.

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

Enable logs
  • Collect Vuser logs from cloud-based load generators.

    Select this check box to collect Vuser logs from the cloud-based load generators used in the load test.

  • Collect Vuser logs from Windows on-premises load generators.

    Select this check box to collect Vuser logs from Windows on-premises load generators used in the load test.

    Note:

    • To enable this option for your tenant, you must open a support ticket.

    • You can only collect Vuser logs from Windows on-premises load generators of version 3.6 or later.
    • The load generator must be configured to collect Vuser logs. For details, see On-premises load generators.

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.

Store extra data for export
  • Store script errors.

    Select this check box to store all the 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.

    Select this check box to store 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.

  • Stream script errors to Splunk.

    Select this check box to enable 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.

Enable multiple IP addresses

Enable 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

  • TruClient

  • 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 StormRunner Load can use them in the load test.

Cloud-based load generators (AWS)

For AWS cloud-based load generators, SRL 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, SRL functions as follows:

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

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

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

  4. If you are using allocated (whitelisted) IP addresses for cloud-based load generators, the IP addresses used for the test will only be taken from the allocated IP address pool. If there are not enough allocated IP addresses to be distributed among the cloud-based load generators, the test will fail.

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):

Disable whitelisted IPs Do not use the allocated whitelist IPs for load generators on the cloud.
Group transactions

When you select this check box, a transaction group is created for all the transactions with the same name in all of the 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.

Note:

  • 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 extra data for export.
Enable script assignment

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 On-premises locations.

Note: This option is applicable only for scripts assigned to an on-premises location.

Accelerate initialization

Select this check box if you want StormRunner Load to search for the load generators that are most likely to launch your load test in the least amount of time.

To enable this feature, open a support ticket.

Limitations:

  • This applies only to Web HTTP 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 LoadRunner Help Center (select the relevant version).

Back to top

Add scripts from your StormRunner Load repository

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

  1. Click the Scripts pane.
  2. Perform one of the following actions:
    ActionHow to
    Add from assets

    Select one or multiple scripts to add from the repository.

    1. Click Add from assets.
    2. Highlight one or more scripts in the Scripts dialog box to add to the test.
    3. Filter scripts by a specific label.

      In the Filter panel, highlight the label to search for.

      Use to search for a label name.

    Upload

    Upload a script to the cloud repository from your local drive.

    1. Click Upload.
    2. Select one or more scripts from the file system to upload and add to your test.
    Duplicate

    To use the same script multiple times, duplicate the selected script and change the configuration. For example, change the number of Vusers from 100 to 400.

    1. Highlight an existing script in the grid.
    2. Click Duplicate.
    Copy scheduling

    Copy scheduling parameters from one script to another:

    1. Select a script with the scheduling information you want to copy.

      Note: When copying from a script that includes advanced scheduling, only target scripts that are compatible with advanced scheduling are enabled for selection. For details on limitations when copying advanced scheduling, see Advanced mode.

    2. Click the button.
    3. Select the script or scripts to be updated.
    4. Click the button to apply the settings to the selected scripts.

    For details on scheduling modes, see Configure the script schedule.

    Runtime settings

    View or edit runtime settings for individual scripts in your test.

    For details on runtime settings, see Runtime settings dialog box.

    Note: When editing and saving runtime settings for a script in a load test, you can select one of the following modes:

    • Local. The settings apply to the script in the current load test only.

    • Global. The settings apply to the script in any load test in which it is included, provided that the script is set to global mode for that specific load test.

    By default, newly uploaded or added scripts are set as local.

    Actions

    Apply script configuration settings to multiple scripts.

    For details, see Configure the script schedule.

    Copy runtime settings

    Copy runtime settings from one script to another:

    1. Select a script with the runtime settings you want to copy.
    2. Click the Copy runtime settings button.
    3. Select the script or scripts to be updated.

      Note: Only scripts in the same load test, and of the same type as the script you are copying from, are displayed.

    4. Click Apply to apply the settings to the selected scripts.

    Note:

    • Only scripts recorded in VuGen have runtime settings.
    • You can only copy runtime settings between scripts of the same type.
    • Only settings configured directly in the Runtime Settings dialog box, and that are common to both the source and target scripts, are copied.

    • Run Logic runtime settings are not copied.
    • Runtime settings are copied from the source script according to its mode (if set to global then global settings are copied and if set to local then local settings are copied). The settings are copied as local settings for the destination script and that script is automatically reset to local mode.
    Activate or deactivate a script

    By default, when you add a script to a load test, it is active. You can deactivate a selected script in a load test by clearing the Active check box for it.

    Deactivating a script keeps it in the load test's configuration and retains the script's runtime settings, but does not include it as part of the load test's runs.

    Deactivated scripts are not included when calculating license usage.

    Note: You must include at least one active script in a load test to be able to run the test.

Back to top

Add scripts from your Git repository

You can connect to an existing Git script repository and add those scripts to your StormRunner Load load tests.

For details, see Git integration.

Do the following to add or update a script from your Git repository to StormRunner Load:

Action How to
Access the Git repository

Click and select Upload from Git to open the Git repository dialog box.

Select an agent

From the drop-down menus, select the agent, repository, and branch that connect to the script repository you want to use.

For details on managing your Git agents, see Agents.

Select a script

Select one or more scripts from the Git repository. Click Add.

Sync Git scripts

Do the following to sync Git scripts:

  1. Select .
  2. Select the scripts you want to sync.
  3. Click to sync your scripts with the Git repository.

Back to top

Configure the script schedule

There are three modes of script schedules—simple, manual, and advanced. For all modes, you configure basic settings described in the table below for each script included in the load test. Only those settings that are applicable to the load test configuration are displayed.

Action How to
Specify the number of VusersA virtual user emulates user actions in your application. Define how many Vusers will perform the business process recorded in your script during the load test.
  1. Click the Vuser column.
  2. Enter the number of Vusers.

Note: For TruClient Native Mobile scripts, only one Vuser runs in the test.

Specify the percentage of VusersA virtual user emulates user actions in your application. Define how many Vusers will perform the business process recorded in your script during the load test.

Note: This setting applies to scripts in a load test that is configured for Goal Oriented mode.

  1. Click the % of Vusers column.
  2. Enter the percentage of the total Vusers for the load test that you want to allocate to run the selected script.

Note: The total for all the scripts in the test must be 100%.

Define the Start time

Define the start time of each script in your test.

If you have several scripts associated with your test, you can set a different start time for each script.

If you do not enter a start time, the script runs at the start of the test.

  1. Click the Start time column.
  2. Enter the time to start running the script after the test begins to run.

Set test duration

Note: This setting applies to scripts in a load test that is configured for Duration mode.

  1. Click the Duration column.

  2. Enter hours, minutes, and seconds (hh:mm:ss).

Note: You cannot configure the test duration when using the Advanced scheduling mode as the duration is calculated automatically (the total time of all the ramp up, duration, and tear down steps).

Set the number of iterations

Note: This setting applies to scripts in a load test that is configured for Iterations mode.

Configure the number of iterations the script should run during the test.

  1. Click the Iterations column.

  2. Enter the number of iterations the script should run during the test.
Set the maximum duration

Note: This setting applies to scripts in a load test that is configured for Iterations mode.

Configure the maximum length of time in which the script should complete the number of configured iterations.

If the script has not completed the number of configured iterations within the maximum duration time, the Vusers for the script are terminated.

  1. Click the Maximum duration column.

  2. Enter hours, minutes, and seconds (hh:mm:ss).

Set the location

Location is the location of the load generators that run the script—Cloud, On Premise, or Private Cloud.

Select the required location from the drop-down menu.

For more details on configuring locations, see Configure load generator locations.

Note:

  • Only those locations that support the specific script type are enabled.
  • When you change the location for a script that is configured for On Premise, if the script is assigned to run on a specific load generator it will automatically be unassigned. For details, see On-premises locations.

You then configure additional settings, either general for all modes or specific to the selected mode, by clicking the arrow to the left of the script name. In the expanded schedule area that opens, select Simple, Manual, or Advanced.

A graph displays a visual representation of the script schedule showing the number of Vusers, duration, ramp up, and tear down. (A much smaller version of the graph is also displayed in the row of the selected script.)

Simple mode

This is the default schedule mode and enables you to configure a time during which the Vusers are started or stopped, at a consistent rate. For example, if you configure ten Vusers for the script and a Ramp up time of ten minutes, one Vuser is started each minute.

Configure the following additional settings directly in the row of the selected script:

Action How to
Define the ramp up

Specify the ramp up time to start Vusers at a consistent rate.

  1. Click the Ramp up column.
  2. Enter hours, minutes, seconds (hh:mm:ss).

Note: For TruClient Native Mobile scripts, only one Vuser runs, so there is no ramp up.

Define the tear down

Specify the tear down time to stop Vusers at a consistent rate.

  1. Click the Tear Down column.
  2. Enter hours, minutes, and seconds (hh:mm:ss).

Note: For TruClient Native Mobile scripts, only one Vuser runs, so there is no tear down.

Manual mode

Note: This mode is disabled for load tests configured for the Iterations run mode.

This mode enables you to simulate a slightly more complex scenario by configuring the ramp up and tear down for a configured number of users in time intervals. For example, you can configure three Vusers to be started every two minutes until all the Vusers for the test have been started.

Select the Manual radio button and configure the following additional settings in the expanded schedule area:

Action How to
Define the ramp up, the rate at which Vusers are added.

Specify how many Vusers are added and at what time intervals.

  1. Specify the time interval.
  2. Specify the number of Vusers to start in each time interval.
Define the tear down, the pace at which Vusers are stopped.

Specify how many Vusers are stopped and in what time intervals.

  1. Specify the time interval.
  2. Specify the number of Vusers to stop in each time interval.

Advanced mode

This mode enables you to configure a schedule that more accurately reflects a real life scenario, with multiple instances of Vusers starting and stopping during the test.

Select the Advanced radio button and then click . In the dialog box that opens, configure multiple steps using the following additional settings:

Action How to
Define the ramp up, the rate at which Vusers are added.

Click to add a Ramp up step and specify how many Vusers are added and in what time intervals.

  1. Specify the time interval.
  2. Specify the number of Vusers to start in each time interval.
  3. Specify to total number of Vusers to start in the step.

For example, you can configure two Vusers to be started every four minutes until a total of twelve Vusers have been started.

Set duration

Click to add a Duration step and specify the time the test will run before executing the next scheduling step.

Duration does not include ramp up and tear down times.

Define the tear down, the pace at which Vusers are stopped.

Click to add a Tear down step and specify how many Vusers are stopped and in what time intervals.

  1. Specify the time interval.
  2. Specify the number of Vusers to stop in each time interval.
  3. Specify to total number of Vusers to stop in the step.

For example, you can configure three Vusers to be stopped every two minutes until a total of nine Vusers have been stopped.

Note:  

  • Advanced mode is not enabled for scripts configured to run on a private cloud location.
  • Advanced mode is disabled for:
    • scripts in a load test configured for the iterations run mode.
    • scripts that contain rendezvous points.
    • TruClient native mobile scripts.
    • scripts with the General settings > Add Vusers option selected. For details, see Set general test settings.
  • The first step must be a Ramp up.
  • The last step must be a Tear down.
  • The schedule must include at least one Ramp up step, one Duration step, and one Tear down step.
  • You can include a maximum of twenty steps in the schedule.

Other additional settings

For any of the schedule modes, you can configure the following additional settings:

Action How to
Set pacing

Controls 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 > Scripts tab or from Runtime settings > Pacing.

To set the pacing in the Load test > Scripts tab:

  1. Open the additional settings area for the script.
  2. Select the Local pacing check box.
  3. Enter time in seconds.

    Tip: To set the time in milliseconds, enter the time in decimals. For example, 250 milliseconds = 0.250.

    Pacing defaults to 1 second.

For LoadRunner scripts, if your script contains fixed pacing, pacing defaults to the script value. You can manually change the value.

To set the pacing using runtime settings, see the Runtime settings dialog box.

Note: If the Local pacing check box is not selected, the runtime settings values are used by default.

Show snapshots

Snapshots are a visual representation of the script. If snapshots are available for a script, the Show snapshots button is displayed. Click the button to view the available snapshots.

Note: Snapshots are only applicable for TruClient scripts.

Back to top

Configure a goal for a load test

You can configure a load test to run in Goal Oriented mode. If you select this option, you configure a goal for the test and when the test runs, it continues until the goal is reached. For more details, see How StormRunner Load works with goals.

To configure a goal oriented test:

  1. In the load test's General page, select Run Mode > Goal Oriented. For details, see Run mode.

  2. In the load test's Scripts page, configure the % of Vusers and Location for each script. For details, see Configure the script schedule.

  3. In the load test's Scripts page, click . In the Goal Settings dialog box that opens, configure the following:

    Setting Description
    Goal type

    Select the goal type:

    • Hits per second. The number of hits (HTTP requests) to the Web server per second.
    • Transactions per second. The number of transactions completed per second. Only passed transactions are counted.
    Transaction name If you selected Transactions per second as the goal type, select or input the transaction to use for the goal.
    Goal value Enter the number of hits per second or transactions per second to be reached, for the goal to be fulfilled.
    Vusers Enter the minimum and maximum number of Vusers to be used in the load test.
    Ramp up

    Select the ramp up method and time. This determines the amount of time in which the goal must be reached.

    • Ramp up automatically with a maximum duration of. Set the maximum duration time in which the goal is to be reached.

    • Reach target number of hits or transactions per second <time> after test is started. Set the specific duration time after the start of the test run when the goal is to be reached.

    • Step up N hits per second every. Set the number of hits per second that are added and at what time interval to add them. Hits per second are added in these increments until the target is reached.

      Note: This option is only available for the Hits per second goal type.

    Action if target cannot be reached

    Select what to do if the target is not reached in the time frame set by the Ramp up setting.

    • Stop test run. Stop the test as soon as the time frame has ended.

    • Continue test run without reaching goal. Continue running the test for the duration time setting, even though the goal was not reached.

    Duration

    Set a duration time for the load test to continue running after the time frame set by the Ramp up setting has elapsed.

    Note: The total test time is the sum of the Ramp up time and the Duration.

The following do not support the Goal Oriented run mode:

  • Adding Vusers.

  • Generating single user performance data.

  • The Timeline tab when scheduling a load test.

  • Network emulations for cloud locations.

  • Changing the load in a running load test.

  • TruClient - Native Mobile scripts.

How StormRunner Load works with goals

StormRunner Load runs Vusers in batches to reach the configured goal value. Each batch has a duration of 2 minutes.

In the first batch, SRL determines the number of Vusers for each script according to the configured percentages and the minimum and maximum number of Vusers in the goal settings.

After running each batch, SRL evaluates whether the goal has been reached or not. If the goal has not been reached, SRL makes a calculation to determine the number of additional Vusers to be added in the next batch.

If the goal has been reached, or there are no remaining Vusers to be added, the ramp up ends. Note that the value can be greater than the defined goal value. SRL does not remove Vusers to reduce the load.

During run time, if the goal was reached, but subsequently drops to below the configured value, SRL will try to add Vusers (if there are any remaining to be added) to reach the goal again.

SRL does not change think time and pacing configured for scripts.

Back to top

Dynamically add additional Vusers during the test run

Optionally, configure the test to enable you to add additional Vusers during the test run.

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

  1. From Load tests > Test settings page, select Enable adding Vusers during a test run.
  2. From the Load tests > Scripts > Add Vusers during the test run page, specify the percentage of Vusers you want to add during the test run.

For details on adding Vusers during the test run, see Dynamically increase or decrease running Vusers during the test run.

Back to top

Add monitors

Add monitors to monitor your load test.

  • Each load test can have only one type of monitoring: SiteScope, SiteScope on-premises, or New Relic.
  • If your test requires SiteScope on-premises or New Relic monitoring, you can add only one monitor per load test.

Click the Monitors pane.

Perform one of the following actions:

Action How to

Create

Click Create to open the New Monitor dialog box.

SiteScope monitor:

  1. Select SiteScope as your monitor type.
  2. Define the monitor by specifying the server name/IP address and username.

For details on configuring a SiteScope monitor, see Monitors.

SiteScope-on-Prem monitor:

If your AUT is behind a firewall, use a SiteScope on Prem monitor to monitor your load test.

Make sure that:

  • A Data integration tag has been set up in SiteScope.

  • A StormRunner Load Monitor Agent has been installed and configured for SiteScope, and that it is started. For details, see StormRunner Load agent.

  1. Click SiteScope on-Prem.

    If the SiteScope on prem tab is disable, check:

    • the StormRunner Load agent connectivity to SaaS
    • the StormRunner Load agent connectivity to SiteScope
  2. Give the monitor a name, and select the SiteScope agent.
  3. Select metrics to monitor.

    Tip: To expand the full list of metrics, click the Expand button.

    In addition to the standard monitors, the following Dynamic Docker monitor types are supported:

    • Docker
    • Cluster Swarm

    When you select a Dynamic Docker monitor type, all metrics are added to your test definition.

  4. Save your selection.

New Relic monitor:

  1. Select NewRelic as your monitor type.
  2. Enter your NewRelic API Key.
  3. Select an application or a server to monitor.
  4. Give the monitor a name, and select metrics to monitor.

    • To expand the full list of measurements, click the Expand button.

    • If there are more than 500 metrics, the Expand/Collapse buttons are disabled.

    • If no measurements are listed, make sure that your New Relic monitor is up and running, and that StormRunner Load is connecting to it.

Dynatrace:

Use a Dynatrace monitor to monitor the applications you are testing and the application servers.

Make sure that:

  • There is a dashboard in Dynatrace containing chart-type dashlets that display the information you want to view in StormRunner Load.

  • A StormRunner Load Monitor Agent has been installed and configured for Dynatrace, and that it is started. For details, see StormRunner Load agent.

  1. Click Dynatrace.
  2. Give the monitor a unique name, and select the Dynatrace agent.
  3. Select measurements to monitor.

    To expand the full list of measurements, click the Expand button.

    If no measurements are listed, make sure your application is up and running and that the measurements are visible in Dynatrace.

  4. Save your selection.

Add from assets
  1. Click Add from assets.
  2. Select one or more monitors to add to the test definition.
Add topology
  1. Click Add topology.
  2. Select one or more topologies from the Add topology from repository dialog box.
Edit
  1. Select a monitor.
  2. Click Edit and modify server details.

Back to top

Configure load generator locations

For each script in the test, you configure a location—Cloud, On Premise, or Private Cloud. This is the location of the load generators that run the script. For details, see Configure the script schedule.

You configure the settings for each location type in the Distribution pane:

  1. Click the Distribution pane.
  2. Click the tab for the location type you want to configure—Cloud, On Premise, or Private Cloud.

Back to top

Configure SLAs

  1. Click the SLA pane.
  2. Select the percentage of transactions expected to complete successfully. The default value is 90%.

  3. Set the percentile TRT (seconds) (transaction response time) value. This is the expected time it takes the specified percent (from step 2) of transactions to complete.

    For example, in your script you have a transaction named "Login". The 90th percentile TRT (seconds) value for this transaction is set to 2.50 seconds. If more than 10% of successful transactions that ended during a 5 second window have a response time higher than 2.50 seconds, an SLA warning is recorded.

    The default percentile TRT (Seconds) value is 3.00 seconds.

    Tip: If you have run your test more than once, StormRunner Load will display a suggested percentile TRT value. Click the button to use the suggested value.

  4. Check Stop test to stop the test if the SLA is broken.
  5. You can clear the Enable option if you do not want a transaction to be monitored during the test run.

Tip: Select multiple SLAs at one time and apply one or more actions to the set.

Back to top

Generate single user performance data

Note: You cannot generate single user performance data for:

  • Load tests configured for the Iterations run mode.
  • Scripts configured to run on on-premises load generators.

When enabled, you can create client side breakdown data to analyze user experience for a specific business process.

Select from one or more of the following report types:

Report type How to
NV Insights

Generate a comprehensive report based on the selected script that provides information about how your application performs for a specific business process.

Generate an NV Insights report:

  1. Select the Single user performance pane.
  2. Under the Client Side Breakdown tab, select the NV Insights check box.
  3. Click Select Script and select a script for the report.

Note: It can take several minutes for the NV Insights report to be generated when viewing it for the first time in a load test.

See also:

TRT Breakdown

Generate TRT breakdown data:

  1. Select the Single user performance pane.
  2. Under the Client Side Breakdown tab, select the Transaction Response Time Breakdown check box.
  3. Click Select Scripts and select up to five scripts.
  4. To display the results, from the Dashboard > , select the Breakdown widget.

For details, see Transaction response time breakdown data.

WebPage

Generate a WebPage report:

  1. Select the Single user performance WebPageTest Report pane.
  2. Under the WebPage Test Report tab, enter a URL of your application. You can add up to 3 URLs.
  3. Select a network speed.

    Network speed Description

    Cable

    5/1 Mbps 28ms RTT
    DSL 1.5 Mbps/384 Kbps 50 ms RTT
    FIOS 20/5 Mbps 4 ms RTT
    56K Dial-Up 49/30 Kbps 120 ms RTT

    Mobile 3G

    1.6 Mbps/786Kbps 300ms RTT
    Mobile 3G- Fast 1.6 Mbps/786Kbps 150ms RTT
    Native Connection No traffic shaping

For details, see WebPage Test report data.

Back to top

Assign labels

Use labels to help you organize scripts in your repository, or to organize your load tests in the Load Tests and Results pages. The labels you create are common to both scripts and load tests.

Labels can be nested in sub-categories:

Click to expand the Labels pane.

You can perform the following actions for labels:

Action How to

Create a label

 

  1. From the Labels pane, select to open the new label dialog box.
  2. Give the label a name.
  3. If desired, nest the label under another label.
  4. Click to select a label color.
Edit a label

From the Labels pane, highlight a label.

Click and select Edit.

Delete a label

From the Labels pane, highlight a label.

Click and select Remove.

Removing a label also removes any sub-labels.

Assign a color to the label

From the Labels pane, highlight a label.

Click and select Color.

Add a sub-label

From the Labels pane, highlight a label.

Click and select Add Sub-label.

Assign a label
  1. From the scripts or load tests grid, highlight one or more rows.
  2. Expand the drop down.
  3. Select the labels to assign to the selected scripts or load tests.

Use to search for a label name.

Filter by a label

Filter scripts or load tests by a specific label.

In the Labels pane, highlight the label to search for.

Use to search for a label name.

Back to top

Schedule a test run

Schedule a test to run on a specific date and time.

Caution: The most up-to-date test settings will be used when the test is launched.

To schedule a test:

  1. From Load Tests page, click the pane.
  2. Click the button.

    Note: You can configure up to 10 schedules for a load test.

  3. From the date picker, select a date to run the test.
  4. From the time picker, specify a time to run the test.
  5. To set the schedule, click .

    The button appears in the cart section indicating that a schedule is set for this load test.

Tip: In the Loads Test page, a test with a set schedule has the icon displayed next to its status.

On the lower part of the page, underneath the list of set schedules, the following two tabs show additional schedule information:

Runs tab

The Runs tab displays a list of previously scheduled runs and their launch status.

  • Launched. The test was launched successfully. Click the run ID to view results.

  • Failed to launch. The test was not launched successfully.

    Troubleshooting failed launches:

    • The number of Vusers scheduled in your test exceeds the amount remaining in your license.

    • A load generator or monitor that is defined in your test is down.

Timeline tab

Note:  

  • This tab is only displayed for tests whose license mode is set as VU.
  • This tab is not displayed for load tests configured for the Iterations run mode.

The Timeline tab displays the timeline for the selected schedule, as well as for any other schedule in the project that overlaps with the selected schedule.

If the current project uses global licenses (that is, it does not have dedicated licenses assigned to it), then schedules from other global license projects that overlap with the selected schedule are also displayed.

The timeline is colored according to its status, as follows:

  • OK (green). There are no conflicts and this schedule will run as planned.

  • Conflicting (orange). This schedule impacts another schedule and will cause it to breach your license count, but this schedule will still run as planned.

  • Blocked (red). This schedule will breach your license count and may not run.

Back to top

Run the test

Click Run Test.

By default, you will receive a report when your test ends.

Back to top

Notes and limitations

  • Before running your load test, always make sure that the monitor defined in the test is up and running and accessible so that it can monitor the test and display results in the dashboard.
  • An on-premises load generator can be occupied by one running test at a time.
  • The number of Vusers defined in your test must not exceed the maximum number of Vusers defined in your Vuser license.

  • The SiteScope agent can be occupied by one running test at a time.

Back to top

See also: