Configuration: Testing: Scenarios
Overview
Use this page to create, edit, and activate test scenarios. A scenario is a saved configuration of user phases and idle phases that defines how many virtual users are active at each point during a load test, and for how long. Instead of ramping users up and down by hand for every run, you define the pattern once and reuse it, so comparable tests produce comparable load.
A scenario's phases draw on the test users you configure elsewhere, and each scenario connects to a profile used when you schedule a run on Testing: Schedules or start one directly from Testing: Run Test. Only one scenario can be the Active Scenario at a time; that is the scenario a run uses by default when none is explicitly selected.
This page lists every scenario as a card with a summary row above it showing the total scenario count, the current Active Scenario, the highest peak user count across all scenarios, and the longest configured duration. From here you can search the list, select New Scenario to build one from scratch, or use a card's Edit button and menu to edit, clone, schedule, activate, or delete it.
Key concepts
- Scenario - A saved configuration of user phases and idle phases that defines how many virtual users are active over time during a load test. (related: Testing: Load Profiles)
- User Phase - A segment of a scenario's timeline during which a set number of virtual users are actively running the test workload. (related: Configuration: Testing: Users)
- Idle Phase - A segment of a scenario's timeline during which virtual users pause without ramping up or down.
- Active Scenario - The one scenario currently flagged to run by default when a test is started without an explicitly chosen profile. (related: Testing: Run Test)
- Randomize - A per-scenario setting that controls whether virtual users within a phase start together or on staggered timing.
When to use it
- Before starting a load test, to confirm which scenario is currently active.
- When you need a new ramp pattern, for example a steady user count or a baseline load, and have to build a scenario from scratch.
- When adjusting an existing scenario's user count, phase timing, or duration without starting over.
- When you want to reuse an existing scenario's phase structure as the starting point for a new one.
- When scheduling a recurring or future run that should use a specific scenario's connected profile.
- When cleaning up scenarios that are no longer used, to keep the list current.
Before you begin
- Know the target virtual user count and ramp timing you want, since these define the scenario's phases.
- If the scenario needs defined test users rather than generic virtual user counts, set those up first on Configuration: Testing: Users.
- If the scenario will be scheduled, confirm you know which recurring pattern you need, since New Schedule carries the scenario to Testing: Schedules pre-filled.
- Have permission to modify test configuration, since Edit, Clone, Set as Active, and Delete change shared test setup.
Common workflows
Confirm which scenario is active before starting a test
Persona: Load-test operator
- Open the Scenarios page.
- Expect: The summary row and card grid load, showing the current Active Scenario value and every configured scenario card.
- Read the Active Scenario value and find the matching card.
- Expect: The card with that name displays the Active status chip next to its title.
- If a different scenario should run instead, open its menu and select Set as Active.
- Expect: The Active status chip moves to that card and the Active Scenario summary value updates to the new scenario's name.
Verify: The Active Scenario summary value matches the card showing the Active chip, confirming the next run will use the intended ramp pattern.
Create a new scenario from an existing one
Persona: Load-test operator or admin
- Open the ellipsis menu on the scenario card closest to the pattern you need and select Clone.
- Expect: A new card appears in the grid with the same phase composition bar, timeline preview, and stat chips as the source scenario, and Total Scenarios increases by one.
- Select Edit on the new cloned card.
- Expect: The scenario editor opens for the cloned scenario.
Verify: The grid shows one more card than before the clone, which you can rename and adjust inside the editor to distinguish it from the original.
Steps
Step 1
Open the Scenarios page.
Expected result: The page loads a summary row showing Total Scenarios, Active Scenario, Peak Users, and Longest Duration, followed by a two-column card grid listing the configured scenarios, each with its phase composition bar, timeline preview, and stat chips.
This gives you the current scenario inventory and shows which one is active before you create, edit, or schedule a test.
- The All Scenarios filter dropdown is set to show every scenario by default.
- The New Scenario button starts a new scenario from scratch.
- Each card's Edit button and ellipsis menu let you edit, clone, schedule, activate, or delete that scenario.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Scenario filter dropdown | Narrows the card grid to a subset of scenarios instead of the default view, useful once you have many scenarios and want to find a smaller group. | dropdown | No | All Scenarios |
| Search scenarios field | Filters the card grid live by scenario name so you can find one quickly instead of scrolling the full list. | free text | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Total Scenarios | Read-only summary of how many scenarios exist in total. | A rising number after you create or clone a scenario confirms the save succeeded; a falling number confirms a delete went through. |
| Active Scenario | Read-only summary showing the name of whichever scenario is currently flagged active. | If this name does not match the scenario you intend to run, use Set as Active on the correct card before starting the test. |
| Peak Users | Read-only summary of the highest Total Users value found across all configured scenarios, not only the ones currently visible in the grid. | Compare it against a card's own Total Users chip to see how that scenario's load ranks against the largest one you have configured. |
| Longest Duration | Read-only summary of the longest Duration value among all scenarios, a single scenario's figure rather than a total. | Use it to spot which scenario runs the longest before comparing individual cards. |
| User Phases | Read-only count of user phases defined inside a scenario's card. | A higher count means more distinct ramp steps, for example ramp up, steady, and ramp down, rather than one flat phase. |
| Idle Phases | Read-only count of idle phases defined inside a scenario's card. | A 0 means the scenario runs continuously with no built-in pause between phases. |
| Total Users | Read-only count of the virtual users this specific scenario ramps up to. | Compare against the Peak Users summary card to see how this scenario ranks among all configured scenarios. |
| Duration | Read-only figure for this scenario's configured runtime. | This is a cap on runtime, not a guaranteed length; the scenario can finish earlier if every virtual user completes its phases first. |
| Randomize | Read-only indicator of whether virtual users within this scenario's phases start on a staggered schedule instead of together. | No means users in a phase start together at the same time; this is the only value captured on this page so far. |
Controls reference
Refresh
Reloads the summary row and the card grid from the server.
When to use: Use it after making a change elsewhere, such as activating a scenario, to confirm the summary stats reflect the latest state.
Side effects: Read-only: it reloads displayed data but does not change any scenario configuration.
New Scenario
Opens the scenario creation flow to define a new set of user and idle phases.
When to use: Use it when none of your existing scenarios match the ramp pattern you need for an upcoming test.
Side effects: Mutating once saved: a new card appears in the grid and the Total Scenarios count increases by one.
Search scenarios field
Filters the card grid as you type, matching against scenario names.
When to use: Use it to find one scenario quickly once the list grows beyond what fits on screen.
Side effects: Read-only: only changes which cards are shown, not any scenario data.
Edit
Opens the selected scenario's phase configuration for editing.
When to use: Use it to change an existing scenario's user count, phase timing, duration, or randomize setting.
Side effects: Mutating only once you save inside the editor; opening it alone makes no changes.
Menu (ellipsis)
Opens a dropdown of additional actions for that scenario card: Clone, New Schedule, Set as Active, and Delete.
When to use: Use it whenever you need an action other than editing the scenario directly.
Side effects: Read-only to open; the mutating effect comes from whichever item you select inside it.
Clone
Duplicates the scenario's phase configuration into a new scenario.
When to use: Use it to reuse an existing ramp pattern as the starting point for a variation, without altering the original.
Side effects: Mutating: adds a new card to the grid and increases Total Scenarios by one.
New Schedule
Navigates to the Schedules page with this scenario's connected profile pre-filled.
When to use: Use it to schedule a run for this scenario without re-selecting its profile manually.
Side effects: Mutating navigation: it opens a new schedule form on another page populated with this scenario's data.
Set as Active
Marks this scenario as the Active Scenario.
When to use: Use it before starting a test when you want this scenario, rather than whichever is currently active, to be the default.
Side effects: Mutating: only one scenario can be active at a time, so the previous Active Scenario loses its status and the Active Scenario summary value updates to this one.
Delete (menu item)
Opens a confirmation dialog for permanently removing the scenario.
When to use: Use it to clean up a scenario you no longer need.
Side effects: Opening it alone makes no change; the removal only happens after confirming in the dialog.
Cancel (delete confirmation)
Closes the delete confirmation dialog without removing the scenario.
When to use: Use it if you opened Delete by mistake or changed your mind.
Side effects: Read-only: no data is changed.
Delete (confirm)
Permanently removes the scenario and its phase configuration.
When to use: Use it only after confirming in the dialog that this is the scenario you intend to remove.
Side effects: Mutating and destructive: the card disappears from the grid and Total Scenarios decreases by one. This cannot be undone from this page.
Verify the result
The Scenarios page lists all configured scenarios as cards, and the Total Scenarios count matches the number of cards you expect after any create, clone, or delete action. The Active Scenario value shows the name of the scenario carrying the Active status chip, and that is the scenario used by default on your next test run. Each card's stat chips, User Phases, Idle Phases, Total Users, Duration, and Randomize, reflect the configuration you last saved in the scenario editor. If a change you made does not appear, select Refresh to reload the summary row and card grid from the server.
Troubleshooting
- Symptom: A scenario you just created or cloned does not appear in the grid. Fix: Check that the scope filter dropdown is still set to All Scenarios, then select Refresh.
- Symptom: The Active Scenario value does not match the scenario you just set active. Fix: Select Refresh to reload the summary row; the card's status chip can update before the summary value does.
- Symptom: You cannot tell two cards apart because a scenario's title is cut off, for example "RDP Baseline - Remote Deskt...". Fix: Open Edit on the card to see the full scenario name before making changes.
- Symptom: Selecting Delete does not remove the scenario right away. Fix: Delete opens a confirmation dialog first; you must select Delete again inside that dialog to finish removing it.
- Symptom: Typing in the search field returns no cards even though the scenario exists. Fix: Reset the scope filter dropdown back to All Scenarios, since a narrower filter combined with a search term can hide a matching scenario.
Related articles
- Prerequisite: Configuration: Testing: Users - Scenario phases reference the test users configured there before you set a realistic Total Users count.
- Next step: Testing: Schedules - New Schedule deep-links a scenario's connected profile into a new schedule.
- Next step: Testing: Run Test - Starting a test uses the current Active Scenario by default.
- See also: Testing: Load Profiles - Each scenario connects to a profile used when scheduling or running a test.
- See also: Configuration: Testing: Wait Events - Wait events configure additional timing behavior used within scenario phases.