Build a VarioTest

This guide walks through composing a VarioTest from tests you already have. It assumes you already know the scenario, weight, and variant model — read that first if the terms are new.

Prerequisites

• Two or more single tests already created in the same project, each individually validated — run each one on its own first so you know it passes before combining it into 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

Because VarioTest has no separate weight field, 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 you want to dominate the traffic, 300 for checkout, 100 for background polling.
3. Confirm each scenario’s locations and capacity plan independently — VarioTest does not share a location plan across scenarios.
4. Save each test’s configuration.

Round numbers, proportional mix

You do not need the totals to sum to a specific number — 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 sources scenarios from within one project. Click Next.
4. Scenarios — a checklist of every single test in the selected project appears. Check the scenarios you want to include, in the order you want them to run — up to 20 — since the selection order becomes the run order. Click Review.
5. Review — confirm the name, project, and ordered scenario list. Click Create VarioTest.

You land on the new VarioTest’s detail page. It behaves like any other test: an Overview, Configuration, Runs, and Schedules tab. The Configuration tab’s Scenarios section shows a read-only table of the constituent scenarios in position order — reordering after creation requires recreating the VarioTest, so double-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 directly. Manage each constituent scenario’s files and secrets by opening that individual 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 (alongside Location, Label, and Runner) to isolate one constituent scenario’s metrics without leaving the combined run.

For the full results-reading walkthrough — including the Metrics, Errors, and Runners tabs — see Runs — read results.

Per-scenario overrides via the API

The console wizard submits each scenario using its own default load profile. If you need to run a VarioTest with a temporary per-scenario override — without editing the underlying test’s saved configuration — use the scenarios payload field documented on the API reference when starting 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.
• Engine mixing is supported. 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 independently.
• Validate each scenario alone first. A scenario that fails on its own will still fail (and can mask interference effects) inside a composite run — smoke-test each one individually before composing.

Where to go next

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