Scenarios and VarioTest

Most real systems are tested with more than one user journey running at the same time. MaxoPerf gives you two ways to express that: scenarios inside a single test, and VarioTest across multiple tests.

Scenarios inside a test

A scenario is a named user journey inside one test. For example, a checkout test might have three scenarios: Browse, Add to cart, and Checkout. Each scenario can have its own request shape, weight, and assertions, but they all share one test definition, one location plan, and one run.

Scenarios are the right level when:

• All journeys belong to the same product surface.
• You want a single run page to show how each journey performed.
• You want to vary the weight of journeys without splitting them into different tests.

Result data is broken down per scenario so you can compare latency, throughput, and errors for each one independently.

Scenarios are configured in the Scenario and files section of the test form — each with its own weight and assertions.

VarioTest — composing multiple tests

VarioTest is the next level up. A VarioTest is a parent test that runs several existing tests at the same time, each with its own runners and load profile. When you start a VarioTest, MaxoPerf starts one child run per included test plus one parent run that aggregates the results.

Use VarioTest when:

• You want to combine independent tests into one execution — for example, a web test and an API test that share the same backend.
• Different journeys need very different runner counts or locations.
• You want one parent run page that summarizes the whole campaign, while keeping per-test detail.

VarioTest preserves the parent–child relationship so you can drill from the campaign view down to each child run.

Creating a VarioTest walks you through picking the tests to combine before it starts one parent run and one child run per test.

Choosing the right level

• One product surface, one team, one run page → scenarios.
• Several existing tests already in production → VarioTest.
• Realistic mixed-traffic simulations → either; VarioTest when the parts already exist as standalone tests.

Where to go next

• Run your first test — covers the single-test path.
• Build reporting dashboards — assemble dashboards that span scenarios and child runs.
• Read run results and logs — drill from the parent run into per-scenario detail.