Scenario Duration and Phase Ending Events

Mode: the create and edit controls described on this page are shown in Expert mode (sidebar footer toggle Mode: Basic / Expert). In Basic mode the page shows only Refresh.

In LoadGen you have several features to build your perfect load or performance test. In the Platform these live in the Scenario editor: navigate to Configuration > Testing > Scenarios and select + New Scenario, or open an existing scenario for editing. Creating one opens the New Scenario page, subtitled Configure phases and ramp settings, with Cancel and Create Scenario in the top-right; editing opens the same editor with the scenario's current settings and phases filled in. A scenario defines the sequence of phases that the platform applies when running a load test, and is linked to (or set as the active default for) your Load Profiles.

Scenario Settings — name, exit type and switches

The scenario-level options live in the Scenario Settings section:

• Linked Scenario — start from an existing scenario or choose Create new scenario.
• Scenario Name — the name the scenario is listed under (for example Default Scenario).
• Exit Type — a dropdown that determines how sessions are ended when the test stops. The options are Default, Disconnect and Logoff.
• Active — a checkbox that makes this the default load shape for runs that don't specify one.
• Randomize Users — a checkbox that introduces randomization into how the scenario draws on your user pool.
• Fixed Duration — a checkbox that caps the test at a total run time instead of letting the phase plan alone decide when it ends.

Phases — shaping the load

Each scenario is built from phases, listed in the Phases section (its heading carries the current phase count). Two buttons add a phase:

• + Users — adds a users phase, which brings virtual users online, holds them, or takes them offline.
• + Idle — adds an idle phase, which waits without changing the load.

Until you add at least one users phase the section warns: "No scenario phases defined: this profile is incomplete. A load test needs at least one Users phase to dispatch sessions."

Below the phase list, the Scenario Actions section (its heading likewise carries a count) lets you attach a script to the scenario: an executable (for example script.exe) with optional arguments (--flag value), run either On Start or On Stop of the test.

The editor itself no longer shows a Visual Timeline or a Wait Event picker; the phase timeline is previewed on each scenario's card in the Scenarios list instead. Wait Events remain a separate configuration page (Configuration > Testing > Wait Events).

Scenario Duration → "Fixed Duration"

With a fixed duration you set the total run time of the test. In the scenario editor, tick the Fixed Duration checkbox under Scenario Settings. When the duration is reached, the platform ends the test according to the configured Exit Type.

A fixed duration supersedes the phase plan

Like the Suite's Scenario Duration, a fixed duration ends the test regardless of where the phase sequence stands.

Phase Ending / Exit Type

Where the Suite used Phase Ending Events (OnUserConnected, OnScriptSuccessful, and so on) to decide when a phase or test could end, the Platform scenario editor controls this with the phase plan plus the Exit Type setting under Scenario Settings.

The dropdown offers Default, Disconnect and Logoff.

Be careful with long iterations

The trade-off is the one the Suite had with OnScriptSuccessful: Logoff ends each session in an orderly way, which can take a long time when your workload iterations are long, while Disconnect cuts the sessions at once and ends the test promptly at the cost of hard-disconnected sessions; Default applies the platform's standard handling. Pick the exit type that matches how strictly the test has to end on time.