Testing: Run Test

Updated

Testing: Run Test

Overview

Use this page to configure and start a load test run from an existing load profile. A load profile packages a scenario (the phases, wait events, and custom actions that define how virtual users ramp and behave) together with the agent that generates the load. Run Test is where you pick which profile, or up to three at once, actually executes and when it starts.

The load profile and its scenario must already exist: profiles are built on Testing: Load Profiles from scenarios configured on Configuration: Testing: Scenarios. Once you start a run here, it appears as the active test on Testing: Active Test, then its history, charts, and LoadGen Score are recorded on Testing: Test Runs.

This page lets you select one to three load profiles, set a Start Mode (Now, At Time, or In Delay), and optionally add a Test Name, Description, Dry Run mode, or a combined chart overlay for multi-profile runs, with the licensed concurrent-user capacity shown before you select Start Test.

Key concepts

  • Load Profiles - A load profile is a pre-configured combination of a scenario and an agent that Run Test launches as a test. You select one or more of these on this page to run. (related: Testing: Load Profiles)
  • Scenario - The phases, wait events, and custom actions that define how a profile's virtual users ramp up and behave during the run. (related: Configuration: Testing: Scenarios)
  • Start Mode - The timing rule for when a run begins: immediately, at a chosen future time, or after a delay you set. (related: Testing: Schedules)
  • Dry Run - A run mode, set with Test Mode (Dry Run), that lets you validate a profile and scenario configuration instead of executing a standard live test.
  • Primary profile - When multiple profiles run together, the primary profile is the one whose datasource stores the combined run's results. (related: Configuration: Datasources)

When to use it

  • Launching a load test immediately from an existing load profile.
  • Scheduling a test to start at a specific future date and time using At Time.
  • Starting a test after a short countdown using In Delay, to give yourself time to open monitoring first.
  • Running up to three load profiles together in one coordinated test.
  • Running a Dry Run to confirm a profile and scenario configuration before committing to a full live test.
  • Naming and describing a run so it is identifiable later in Test Runs, reports, and the LoadGen Score.

Before you begin

  • At least one load profile must exist, created on Testing: Load Profiles.
  • The load profile should reference a scenario (phases, wait events, custom actions) configured on Configuration: Testing: Scenarios; a profile with no scenario assigned still runs but falls back to the globally active scenario instead of its own ramp.
  • Your account needs permission to view and run load profiles; without it the panel shows a permission message instead of the checkbox list.
  • Enough licensed concurrent-user capacity for the users you plan to run, shown in the Licensed for N concurrent users badge and managed on Infrastructure: Licensing.
  • If you plan to select more than one profile, confirm they do not share an agent (agents are configured under Configuration: LoadGen Agents).

Common workflows

Start an immediate single-profile test

Persona: Load-test operator

  1. Select the checkbox for the load profile you want to run, for example Test: LoadGen Demo, under its technology group.
    • Expect: The counter above the list updates to 1 of 3 selected, and the scenario preview panel on the right replaces its empty state with that profile's scenario chart.
  2. Leave Start Mode set to Now.
    • Expect: No Start At or Start In field appears, since Now needs no extra timing input.
  3. Optionally enter a Test Name and Description.
    • Expect: The text you type appears in the Test Name and Description fields as typed.
  4. Select Start Test.
    • Expect: The button label changes to Starting..., then the page switches to a Test Started Successfully confirmation with Start Another and View Active Test options.

Verify: The confirmation heading reads Test Started Successfully, and View Active Test opens Testing: Active Test showing the run you just launched in progress.

Schedule a delayed multi-profile test

Persona: Operator coordinating a multi-profile test

  1. Select checkboxes for up to three load profiles that do not share an agent.
    • Expect: The counter updates, for example to 2 of 3 selected, and the scenario preview area shows each selected profile's scenario.
  2. Select the In Delay option under Start Mode.
    • Expect: A Start In field with a Seconds placeholder appears below the Start Mode options.
  3. Enter the number of seconds to wait, for example 60, in Start In.
    • Expect: The value you type is stored as the countdown length for this run.
  4. Select Overlay all profiles in one chart to compare the selected profiles' ramps together.
    • Expect: The scenario preview redraws the selected profiles into a single combined chart instead of separate ones.
  5. Select Start Test.
    • Expect: The run is accepted and will start automatically once the configured delay elapses; the confirmation screen reflects the scheduled start.

Verify: Testing: Active Test shows the run transition from pending to running once the delay elapses, with all selected profiles listed under the one test.

Validate a scenario with a Dry Run

Persona: Operator preparing a new scenario before a live test

  1. Select the load profile whose scenario you want to validate.
    • Expect: The scenario preview panel shows that profile's configured phases and wait events.
  2. Select Test Mode (Dry Run).
    • Expect: The run is marked to execute as a Dry Run instead of a standard live test.
  3. Select Start Test.
    • Expect: The page confirms the Dry Run has started, letting you check the profile and scenario configuration before running it live.

Verify: The confirmation and Testing: Active Test identify the run as a Dry Run, distinguishing it from standard live runs recorded on Testing: Test Runs.

Steps

Step 1

Open Run Test from the left navigation.

Expected result: The page loads showing the Load Profiles panel with 0 of 3 selected and an empty scenario preview panel prompting you to select a load profile to view the scenario.

This is the starting point for configuring and launching a new load test from an existing profile.

  • Load Profiles shows 0 of 3 selected until you check at least one profile under its group, for example TESTCLIENT.
  • Start Mode defaults to Now; At Time and In Delay are also available.
  • The scenario preview panel stays empty, reading Select a load profile to view the scenario, until you check a profile.
  • The green badge reads Licensed for 50 concurrent users, showing your current license ceiling before you select profiles. Testing: Run Test - step 1

Field reference

Field Purpose Format / Validation Required Default
Load Profiles Choose which load profile(s) this run executes. Selecting more than one (up to 3) runs them together in one coordinated test, each on its own timeline from T0, with results consolidated in the primary profile's datasource; selecting one runs a standard single-profile test. Checkboxes grouped by technology/group name, for example TESTCLIENT. Yes none selected (0 of 3)
Start Mode Decide when the run begins. Now starts it immediately when you select Start Test. At Time schedules a single start at a specific date and time you set in Start At. In Delay starts the run automatically after a countdown you set in Start In, useful for giving yourself time to open monitoring before load begins. Radio button group: Now, At Time, In Delay. No Now
Start At Set the exact date and time the run should start. Only relevant when Start Mode is At Time; this is how you schedule a single future start instead of starting now. Date and time value, shown only when At Time is selected. - -
Start In Set how many seconds to wait after selecting Start Test before the run begins. A longer delay gives you more time to prepare monitoring or coordinate with a team before load starts. Numeric input in seconds, placeholder Seconds, shown only when In Delay is selected. - -
Test Name (optional) Give the run a name you will recognize later. Leaving it blank auto-names the run after its profile and start time; a clear custom name is easier to find in results, reports, and the LoadGen Score. Single-line text, placeholder Give your test a name. No blank (auto-named)
Description (optional) Add free-text notes about the run's purpose or context, useful when reviewing it later. Multi-line text area, placeholder Add notes about this test run. No blank
Test Mode (Dry Run) Choose whether this run executes as a standard live test or as a Dry Run. Use Dry Run to validate the selected profile(s) and configuration before committing to a full live test. Checkbox/toggle. No off (live run)
Overlay all profiles in one chart When more than one profile is selected, choose whether their scenario previews are drawn as one combined chart (overlay) or shown separately. Overlay makes it easier to compare ramps at a glance; separate charts make it easier to read each profile's own detail. Checkbox, relevant only when 2 or more profiles are selected. No off

Controls reference

Start Test

Submits the selected load profile(s) and configuration to begin the run, either immediately or per the chosen Start Mode.

When to use: After selecting at least one load profile and setting Start Mode, name, description, or Dry Run as needed.

Side effects: Mutating: launches or schedules a live test execution, consumes license capacity and agent resources, and switches the page to a Test Started Successfully confirmation.

Start Another

Resets the Run Test form after a run has started so you can configure and launch another test.

When to use: After a test has started and you want to start a second one without navigating away.

Side effects: Non-mutating to the test already started; clears the current form selections and returns to the profile-selection screen.

View Active Test

Opens Testing: Active Test for the run that was just started, or for a run already active.

When to use: To monitor live metrics for a run in progress right after starting it.

Side effects: Read-only navigation; does not change the run.

Retry

Re-attempts to load the list of load profiles after a failed load.

When to use: When the page shows a failed-to-load state instead of the Load Profiles list.

Side effects: Read-only refresh; no test configuration is affected.

Check again

Re-checks server-side ingestion capacity before you start a run.

When to use: When a capacity warning indicates the backend may not keep up with the incoming test data for your selected configuration.

Side effects: Read-only refresh of the capacity check; does not start or change a run.

Increase to [worker count]

Raises the available worker/agent capacity to the level your selected load profile(s) require.

When to use: Shown when the combined virtual-user load of your selected profiles exceeds the currently available workers/agents.

Side effects: Mutating: changes agent/worker allocation and shows an Applying... state while in progress.

Go to License Management

Opens Infrastructure: Licensing.

When to use: Shown when your selected configuration exceeds the licensed concurrent-user count.

Side effects: Read-only navigation.

Verify the result

A successfully started run replaces the configuration form with a Test Started Successfully confirmation, offering Start Another and View Active Test. Selecting View Active Test opens Testing: Active Test and shows the run with the profile(s), name, and start time you configured. If nothing happens after selecting Start Test, first check whether the Load Profiles counter still reads 0 of 3 selected, or whether a license or capacity warning replaced the Start Test control. Once the run finishes, it is listed on Testing: Test Runs under the name you gave it or its auto-generated name.

Troubleshooting

  • Symptom: Start Test does nothing or stays disabled. Fix: Select at least one checkbox under Load Profiles; the counter must read at least 1 of 3 selected.
  • Symptom: The Licensed for N concurrent users badge is replaced by a Go to License Management link. Fix: Your selected profiles exceed the licensed concurrent-user count; follow the link to Infrastructure: Licensing or reduce the number of profiles or users.
  • Symptom: The Load Profiles panel shows a permission message instead of the checkbox list. Fix: Ask an administrator to grant load-profile permissions; this is controlled on Operations: Permissions.
  • Symptom: A selected profile's scenario preview looks minimal or generic. Fix: The profile has no scenario of its own assigned and is falling back to the globally active scenario; assign one explicitly on Configuration: Testing: Scenarios.
  • Symptom: A warning badge appears when you try to select a second or third profile. Fix: Profiles run together must not share an agent; choose profiles tied to different agents or review agent assignment on Testing: Load Profiles.
  • Symptom: After selecting Start Test you see a capacity warning with a Check again button instead of the run starting. Fix: Wait for backend ingestion capacity to recover, then select Check again before retrying Start Test.
Was this article helpful?
0 out of 0 found this helpful