Testing: Run Test
Overview
Use this page to configure and start a load test run. A load profile is a pre-configured test definition built from a scenario of phases, wait events and custom actions; Run Test turns one or more profiles into an actual execution with a start time you control.
Before you can run anything here, at least one load profile must exist on Testing: Load Profiles, built from a scenario configured on Configuration: Testing: Scenarios, with any credentials it needs set up on Configuration: Credential Profiles. Once a run starts, it appears on Testing: Active Test while in progress, then on Testing: Test Runs and in Analyse: Reports once finished.
On this page, you select up to three load profiles to run together, choose whether the run starts now, at a scheduled time, or after a delay, and optionally name the run. The page also surfaces warnings up front, for example a test already running or a credential close to expiring, so you can resolve them before you start.
Key concepts
- load profile - A pre-configured test definition, built from a scenario, that describes the clients, workload and agents a test should use. Checking one in the Load Profiles list loads its scenario preview on this page. (related: Testing: Load Profiles)
- scenario - The phases, wait events and custom actions that define how a load profile ramps and behaves during a run. (related: Configuration: Testing: Scenarios)
- primary profile - When you select more than one load profile to run together, the first one checked is treated as the primary profile, and its datasource is where the combined run's results are stored. (related: Configuration: Datasources)
- Test Mode (Dry Run) - An option to start the run as a dry run instead of a normal scored test, for validating a profile's configuration before committing to a full run.
- credential profile - A stored authentication credential, such as an API token, that a load profile may depend on. Run Test warns you here when one is close to expiring. (related: Configuration: Credential Profiles)
When to use it
- You need to start an ad hoc load test run outside of a scheduled trigger.
- You want to run up to three load profiles together in one coordinated test.
- You want to validate a load profile's configuration with Test Mode (Dry Run) before running it for real.
- You need to check whether another test is already running before starting your own.
- You see a credential expiry warning and need to decide whether to reissue it before starting a run that depends on it.
- You want to schedule a run for a specific time or after a delay instead of starting it immediately.
Before you begin
- At least one load profile exists, created on Testing: Load Profiles.
- The load profile's scenario (phases, wait events, custom actions) is configured on Configuration: Testing: Scenarios.
- Any credentials the profile needs are valid; check Configuration: Credential Profiles if a 'Credentials expiring' warning appears.
- If you plan to select more than one load profile, confirm they do not share an agent, since profiles sharing an agent cannot run together.
- No other test is currently in the Running state; Start Test stays disabled until it finishes.
- Your account has permission to view and start load tests, and the load testing module (LG050 API Base) is licensed for at least one user.
Common workflows
Start a single load profile test now
Persona: Load-test operator
- Check the box next to the load profile you want to run, for example Test: LoadGen Demo.
- Expect: The counter above the list changes from '0 of 3 selected' to '1 of 3 selected', and the right-hand panel loads that profile's scenario preview instead of the empty placeholder.
- Leave Start Mode set to Now and, optionally, type a name into Test Name (optional).
- Expect: The typed text replaces the 'Give your test a name' placeholder in the field.
- Select Start Test.
- Expect: LoadGen launches the run; the form is replaced by a Test Started Successfully confirmation offering Start Another and View Active Test.
Verify: The Test Started Successfully confirmation appears, and the new run is visible and active on the Testing: Active Test page.
Run multiple load profiles together
Persona: Load-test operator combining workloads
- Check the boxes for two or three load profiles that do not share an agent.
- Expect: The counter updates accordingly (for example '2 of 3 selected'), and the right-hand panel shows a combined scenario preview for the selected profiles.
- Select Overlay all profiles in one chart to compare their live curves on a single chart.
- Expect: The checkbox shows as selected, which determines how the live chart renders once the run starts.
- Select Start Test.
- Expect: The combined run starts, with each profile's timeline beginning at T0.
Verify: The Active Test view shows all selected profiles running under one test, each contributing its own curve, with results recorded against the primary profile's datasource.
Steps
Step 1
Open Run Test.
Expected result: The page loads with the Load Profiles list grouped by technology, a warning that a test (Test: LoadGen Demo) is already running and that Start Test is disabled until it finishes, and a Credentials expiring notice for a token nearing expiry.
This is the starting point for configuring and launching a new load test run.
- Load Profiles shows '0 of 3 selected' until you check a box.
- The warning banner links to View active test and Check again.
- The Credentials expiring notice names the affected token and where to reissue it.
-
Start Mode defaults to Now.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Load Profiles | Selects which load profile(s) to launch in this run. Checking a single profile runs it alone; checking two or three runs them together in one test, each on its own timeline starting at T0, useful for combining complementary workloads into a coordinated run. Profiles that share an agent cannot be combined. | checkbox list grouped by technology heading | Yes | none selected |
| Start Mode | Controls when the run begins. Now starts the run as soon as you select Start Test; At Time schedules it for a specific future timestamp; In Delay starts it after a countdown. Use At Time or In Delay to align a run with a maintenance window or off-peak period without staying at the console. | radio buttons: Now, At Time, In Delay | No | Now |
| Start At | Sets the exact date and time the run starts, shown only when Start Mode is At Time. Use it to align the test with a planned change window instead of starting it manually at that time. | date/time field | No | - |
| Start In | Sets how many seconds to wait after you select Start Test before the run actually begins, shown only when Start Mode is In Delay. A short delay gives you time to switch to a monitoring view before load hits the system under test. | numeric field (seconds) | No | - |
| Test Name (optional) | Labels this run in results, reports and the LoadGen Score. Leave it blank to auto-name the run after its profile and start time; set an explicit name when you need to find or compare this run later. | free text | No | auto-generated from profile name and start time |
| Description (optional) | Adds free-text notes about this run, for example what changed since the last test, for teammates reviewing results later. | free text | No | - |
| Test Mode (Dry Run) | Starts the run as a dry run instead of a normal scored test. Enable it to validate a profile's configuration and connectivity; leave it off for a normal, fully scored test. | checkbox | No | off |
| Overlay all profiles in one chart | When more than one load profile is selected, draws all of their live charts on a single combined chart instead of separate charts per profile, making their curves easier to compare side by side during the run. | checkbox | No | - |
Controls reference
Check again
Re-checks whether the test currently blocking Start Test has finished.
When to use: Use it after the 'test already running' warning appears, once you expect that run to have completed, instead of reloading the page.
Side effects: Read-only: refreshes the active-test status shown in the warning banner; does not start or stop any test.
View active test
Opens the Active Test page for the run that is currently blocking Start Test.
When to use: Use it to inspect or stop the currently running test before you can start your own.
Side effects: Read-only navigation; does not affect the running test.
Close
Dismisses the Credentials expiring notification.
When to use: Use it once you've noted or already reissued the expiring credential, to clear the notice from view.
Side effects: Read-only: hides the notice for this session; does not reissue or renew the credential.
Start Test
Launches a new test run using the selected load profile(s), start mode, and optional name, description, and dry-run settings.
When to use: Use it once you've selected at least one load profile and configured the run options.
Side effects: Mutating: starts a new load test execution, or schedules/delays it per Start Mode. Disabled while another test is already running; shows a 'Starting...' state while the request is in progress.
Increase to
Raises server-side ingestion worker capacity to the suggested level when a pre-test ingestion capacity warning appears.
When to use: Use it when the server warns that current ingestion capacity may not keep up with the run you're about to start.
Side effects: Mutating: changes ingestion worker capacity; shows an 'Applying...' state while the change is in progress.
Retry
Reloads load profile or scenario data that failed to load.
When to use: Use it when a 'Failed to load' message appears instead of the Load Profiles list or scenario preview.
Side effects: Read-only: re-fetches the failed data; does not change any test configuration.
Start Another
Resets the Run Test form after a run starts, so you can configure and launch another run.
When to use: Use it right after a test starts when you need to queue up a different run.
Side effects: Clears your current form selections; does not affect the run you already started.
View Active Test
Opens the Active Test page for the run you just started.
When to use: Use it to watch the new run's live progress instead of starting another one.
Side effects: Read-only navigation.
Verify the result
After you select Start Test, the form is replaced by a Test Started Successfully confirmation, and the new run becomes visible on the Active Test page in the state you expect, such as Running. If Start Test stays disabled, check the warning banner for a test that is still running, use View active test to confirm its state, then select Check again once it has finished. If the run doesn't appear on Active Test shortly after starting, confirm Load Profiles still shows your selected profile and that no permission or licensing message has replaced the list.
Troubleshooting
- Symptom: The Start Test button is disabled and a warning says a test is already running. Fix: Select View active test to check its status, wait for it to finish, then select Check again to re-enable the form.
- Symptom: The Load Profiles list is empty or shows a permission message instead of your profiles. Fix: Confirm your account has permission to view load profiles, or create one on Testing: Load Profiles.
- Symptom: The Credentials expiring notice keeps appearing for a token your test depends on. Fix: Reissue the credential under Configuration: Credential Profiles before starting the run, then dismiss the notice with Close.
- Symptom: You can't check a second or third load profile. Fix: Confirm the profile doesn't share an agent with one you've already selected; profiles sharing an agent cannot run together.
- Symptom: Selecting Start Test fails with a licensing message. Fix: Check Infrastructure: Licensing for the LG050 (API Base) module with at least one licensed user.
- Symptom: The right-hand scenario preview stays on 'Select a load profile to view the scenario'. Fix: Check at least one box under Load Profiles; the preview only loads once a profile is selected.
Related articles
- Prerequisite: Testing: Load Profiles - load profiles must be created here before they can be selected on Run Test
- Prerequisite: Configuration: Testing: Scenarios - scenarios define the phases, wait events and custom actions a load profile runs
- See also: Configuration: Credential Profiles - reissue credentials flagged as expiring on this page
- Next step: Testing: Active Test - view and manage the run once it starts
- Next step: Testing: Test Runs - review completed run history and results
- See also: Testing: Schedules - schedule recurring runs instead of starting them manually