Skip to content

Launching a test

To launch a test, click on the Launch test button from the execution scenario page. The launch test wizard appears:

Virtual Users Validation

Virtual Users validation

The first step is to execute a sanity check of each virtual user. This step validates that none of your Virtual Users contains critical errors. Such errors, like a missing CSV variable file, would prevent the test from running. You need to fix them before continuing to the next step.

Tip

You can click on Open virtual user to open this Virtual User and proceed to a validation in order to see the list of sanity check messages.

Monitoring Connections Validation

Monitoring connections validation

The second step is the monitoring connections validation. If you configured monitoring connections, OctoPerf automatically checks every enabled connection before launching the test.

Before starting the test, you need to either:

  • Fix any connectivity issue,
  • Disable the invalid monitoring connections.

Tip

You can click on the magnifier icon to open any Monitoring Connection.

Start test

Launch test

The final step allows to select:

  • The report name,
  • The report template (only visible if at least one template is available),
  • The subscription to use.

Tip

Leave the Template field blank to use the default one. You can also switch to an other template while the test is running or completed.

Subscription selection

Click on the Launch Test button, the test startup procedure is shown within seconds. Please allow up to a few minutes for the test to start.

Test starting

test-launching

Once all your load generators are green, the tests will start shortly. You can see more details through the Show logs button on top.

Check VU warnings Check VU errors Monitors not validated

Depending on the outcome of previous steps, certain messages may appear at the top of the screen to alert you to potential problems.

Key points to remember:

  • Check VUs: Sanity check errors are blocking. You cannot launch a test while there are sanity check errors (Error level).
  • Check Monitors: All enabled monitors must be functional. If any monitor check fails, you will not be able to launch the test.

No-Auto scaling Messages

No Auto-Scaling Info No Auto-Scaling Info - Usages No Auto-Scaling Warning - Scenario Requirement No Auto-Scaling Warning - Too Much Usage

These messages appear when your scenario uses a location provided by a fixed-capacity On-Premise provider (without auto-scaling).

Info

Auto-scaling is inherently unavailable for On-Premise providers. Their capacity depends on your own infrastructure — specifically:

  • The number of distinct machines (each with one agent installed).
  • The amount of declared and available memory on those machines.

For this reason, OctoPerf displays key information about the required and already used capacity for these providers.

Possible messages include:

  • Info: Your scenario uses provider(s) without Auto-Scaling, but everything is fine and no activity is detected.
  • Info: Your scenario uses provider(s) without Auto-Scaling, everything is fine, but activity is detected.
  • Warning: Your scenario uses a provider with insufficient capacity without any activity.
  • Warning: Your scenario uses a provider with insufficient capacity while other tests are consuming part of it.

In all of these cases, launching the test is still allowed. However, if a warning is displayed, it is strongly recommended to inspect the providers before continuing.

Info

You can refresh or reload the message to recompute the No Auto-Scaling status using the Refresh button located at the top-right of the message.

Inspect Providers

Inspect Providers Dialog

Clicking the Inspect Providers button opens a dialog containing key information about:

  • The No Auto-Scaling providers and their scenario requirements.
  • The currently used capacity of these No Auto-Scaling providers.

Info

This information helps you determine whether sufficient memory is available for your test and, if not, why memory is missing:

  • Because other tests are already using the providers.
  • Because the provider’s total capacity is too limited, regardless of external usage.

Memory Calculation Overview

Detailed values for required and available memory are not displayed. However, the computation takes multiple factors into account, including:

  • VU memory type — Depending on the type of Virtual User (Standard, Heavy, or Browser-Based), memory usage per VU can vary significantly.
  • Number of active agents per provider location.
  • Provider configuration parameters, such as:
    • Total memory available per agent
    • Base memory allocation
    • Memory required per VU
    • Maximum allowed memory utilization (percentage limit)
  • Current memory usage — Memory already consumed by other running tests.

Tip

In most cases, memory issues occur because:

  • Other tests are currently running and consuming part of the provider’s capacity. The dialog shows detailed usage information, including the username, workspace, and project for each active test.
  • The provider is misconfigured, especially regarding the “Amount of memory per agent (MB)” setting, which may not match the actual available memory on the physical machine. (Check the Memory Configuration of the provider, or contact your administrator if you don’t have permission.)

No subscription found

launch-check-subscription-fail

If your current runtime is above the capacity of all your licenses, you will be prompted with the above error. You can either change the runtime to lower the parameter that is too high (duration, VUs or number of profiles) or purchase a bigger license for the duration of your tests.