Build a VarioTest

This guide builds a VarioTest from tests you already have. It assumes you know the scenario, weight, and variant model. Read that first if the terms are new.

1. 0:02 Realistic traffic mix — browse-heavy + checkout-light members
2. 0:51 Browser + protocol hybrid — a few real browsers plus many API users
3. 1:39 The same test, different configurations — e.g. two regions or two load levels
4. 2:26 Master verdict — per-member results and drilling into one member's run
5. 3:14 Re-run and adjust member weights

Build a VarioTest.

Prerequisites

• Two or more single tests in the same project, each validated on its own. Run each one alone first so you know it passes before you add it to a composite run. See Tests: create and configure if you need to create one.
• A MaxoPerf plan with the VarioTest entitlement enabled. If New VarioTest does not appear in the Tests catalog header, ask your workspace admin to check your plan.

Step 1: Size each scenario’s load before composing

VarioTest has no separate weight field, so set the relative size of the mix on each constituent test first:

1. Open each single test you plan to include and go to its Configuration tab.
2. Under Load configuration, set the total virtual users each scenario should contribute to the mix. For example, 600 for a browsing scenario that should carry most of the traffic, 300 for checkout, 100 for background polling.
3. Confirm each scenario’s locations and capacity plan separately. VarioTest does not share a location plan across scenarios.
4. Save each test’s configuration.

Round numbers, proportional mix

The totals don’t need to sum to a specific number, because the mix is proportional. 600 / 300 / 100 produces the same 60 / 30 / 10 split as 60 / 30 / 10.

Step 2: Create the VarioTest

1. In the console, go to Tests in the left navigation sidebar.
2. Click New VarioTest in the catalog page header. (If the button is not present, the entitlement is not enabled on your plan.)
3. Name and project: give the composite test a name (for example E-commerce — mixed workload) and select the project that contains the single tests you want to combine. VarioTest only takes scenarios from one project. Click Next.
4. Scenarios: a checklist shows every single test in the selected project. Check up to 20 scenarios in the order you want them to run, because the selection order becomes the run order. Click Review.
5. Review: confirm the name, project, and ordered scenario list. Click Create VarioTest.

New VarioTest wizard, Scenarios step. MaxoPerf adds checked tests to the composite run in the order you select them.

You land on the new VarioTest’s detail page. It works like any other test, with Overview, Configuration, Runs, and Schedules tabs. The Scenarios section of the Configuration tab shows a read-only table of the constituent scenarios in position order. To reorder after creation you must recreate the VarioTest, so check the order in the Review step.

Files and secrets live on each scenario test

A VarioTest does not own scenario files or workspace secret bindings. Manage each constituent scenario’s files and secrets by opening that test. The VarioTest’s Files and Data tabs point you there.

Step 3: Run and read the results

1. On the VarioTest detail page, click Run VarioTest.
2. A confirmation dialog asks whether to open the run detail immediately or stay on the test.
3. On the run detail page, the Overview tab aggregates throughput, latency, and error metrics across every constituent scenario by default.
4. Use the Scenario scope filter (next to Location, Label, and Runner) to isolate one constituent scenario’s metrics without leaving the combined run.

VarioTest run, Overview tab. The Scenario filter isolates one constituent scenario's metrics inside the combined run.

The full guide to reading results, including the Metrics, Errors, and Runners tabs, is Runs: read results.

Per-scenario overrides via the API

The console wizard submits each scenario with its own default load profile. To run a VarioTest with a temporary per-scenario override, without editing the underlying test’s saved configuration, pass the scenarios payload field documented in the API reference when you start the run.

Tips & gotchas

• VarioTest scenario order matters and locks at creation. Set it in the Review step; recreate the VarioTest to change it later.
• You can mix engines. One scenario can run on Taurus while another runs on k6 in the same composite run. Each keeps its own engine.
• Files, secrets, and locations are per-scenario. There is no shared configuration surface; edit each constituent test on its own.
• Validate each scenario alone first. A scenario that fails on its own also fails inside a composite run, and it can hide interference effects. Smoke-test each one before you combine them.

Where to go next

• Worked example: mixed traffic: a full e-commerce mix from end to end, including an A/B variant pattern.
• Tests: create and configure: the full Tests surface guide.
• Tests & builders: where VarioTest fits next to performance, functional, and browser test builders.