Tests — create and configure

What this is

The Tests surface is where you define, configure, and launch load tests. A test is a reusable definition that captures the scenario files, load profile, runner locations, failure criteria, and secret bindings that every run inherits. You create a test once and run it many times. A single-engine test drives one scenario file; a VarioTest chains multiple single tests into one coordinated multi-scenario run.

Where to find it

Select Tests in the left navigation sidebar. The group expands to show:

• All tests — the test catalog for the active workspace.
• New test — the single-test authoring wizard.

A New VarioTest button also appears in the catalog page header when your account has the VarioTest entitlement.

---

All tests (test list)

The test list shows every test in the active workspace as a compact table. Columns are Test (name, inline-editable), Engine / kind (for VarioTests the kind shows “Vario” with a scenario count), Last run (timestamp in your local timezone), and an Open action link.

Tests list: the full test catalog for the active workspace, with filters above and a paginated table below.

Filters

Four filter controls appear above the table:

Filter	What it narrows
Search	Test name or id (substring, case-insensitive)
Test kind	All kinds · Single tests · VarioTest only
Engine	All engines or a specific Taurus executor (JMeter, k6, Selenium, Apiritif, …)
Project	All projects or a single project in the workspace

How to use the test list

1. Select a workspace using the scope switcher in the top bar — the list is blank without one.
2. Type in Search to narrow by name or paste a test id.
3. Use Test kind to isolate VarioTests from single tests.
4. Use Engine to find all JMeter or k6 tests at once.
5. Use Project to scope the catalog to a single project.
6. Click Open in any row to go to that test’s detail page.
7. Click a test name inline to rename it without leaving the list — press Enter to save.
8. Use the pagination bar at the bottom to page through large catalogs.

Workspace scope required

The test list only loads when a workspace is selected in the top-bar scope switcher. If you see a “No workspace” empty state, select a workspace first.

---

New test

The New test wizard creates a single-engine load test. Navigate to Tests → New test in the sidebar, or click the New test button in the catalog page header.

New test wizard: four sections scroll top-to-bottom. Use the jump-to links at the top to navigate between sections.

The wizard is a single scrolling page with four sections. Jump-to links at the top let you scroll to any section directly:

1. Test details

Field	Required	What it sets
Test name	Yes (≥ 2 characters)	The display name for this test
Project	Yes	Which project the test belongs to

Try-URL quick start

If you arrive at the New test page from the Try URL flow (e.g. from the marketing site), the URL is pre-filled as a quick-start hint banner at the top of the form. The name is also pre-populated as “Load test: <hostname>”. Attach a scenario file that targets that hostname to get started quickly.

2. Scenario and files

Drag and drop your scenario files into the drop zone, or click to open a file picker. Supported file types are detected automatically (Taurus YAML, JMX, k6 JS/TS, Apiritif Python, and supporting assets). Once files are recognised, a File roles list appears letting you set each file’s role (primary scenario vs. test asset).

3. Load configuration

Setting	What it controls
Total virtual users	Concurrent VUs spread across all locations according to weights
Max VUs per runner	Cap per individual runner; MaxoPerf computes the minimum runner count from this
Ramp-up (seconds)	Time to linearly increase load from 0 to target VU count
Stop mode	Duration (run for N seconds) or Iterations (run for N request iterations)
Duration / Iterations	The corresponding stop value

4. Locations and capacity

Add one or more rows to the location plan using Add row. Each row is either a managed region (cloud provider + region) or a BYOC private datacenter. Set a runner count and weight per row — the weight controls how virtual users are distributed across locations. Click Auto-balance to set runner counts automatically based on the total VU target and the max VUs per runner cap.

How to create a new test

1. Navigate to Tests → New test in the sidebar.
2. Fill in Test name and select a Project in the Test details section.
3. Drop your scenario file(s) into the Scenario and files drop zone. Wait for the engine to be detected (a badge appears showing the detected engine).
4. Set file roles if more than one file was uploaded.
5. Adjust Total virtual users, Max VUs per runner, Ramp-up, and Stop mode in Load configuration.
6. Add at least one row to the location plan and set a runner count.
7. Click Create test in the sticky footer. You land on the new test’s detail page.

Engine detection

The test engine is inferred from the scenario file format — you do not select an engine manually. If the engine cannot be detected, an error appears on the drop zone. See Engines — Taurus, JMeter, k6 for details on supported formats.

---

New VarioTest

A VarioTest combines multiple single tests (scenarios) from a single project into one coordinated run. This is available on accounts with the VarioTest entitlement. Click New VarioTest in the catalog page header, or navigate to Tests → New VarioTest directly.

New VarioTest wizard: three steps — Name and project, then Scenarios (pick up to 20 single tests), then Review and create.

The wizard has three steps:

Step 1 — Name and project: Give the VarioTest a name (≥ 2 characters) and select the project that contains the single tests you want to use. VarioTest only sources scenarios from within one project.

Step 2 — Scenarios: A checklist of all single tests in the selected project appears. Check up to 20 tests in the order you want them to run. The selection order becomes the scenario order. You can reorder in the Review step.

Step 3 — Review: A summary shows name, project id, and the ordered scenario list. Click Create VarioTest to submit. You land on the new VarioTest’s detail page.

How to create a VarioTest

1. Click New VarioTest in the catalog page header. (If the button is not present, the entitlement is not enabled — contact your admin.)
2. Enter a name and select the project that holds your scenario tests. Click Next.
3. Check the scenario tests in the order you want them to run (up to 20). Click Review.
4. Confirm the scenario list and click Create VarioTest.

Per-scenario load overrides

The wizard submits each scenario using its default load profile. Per-scenario load overrides (custom VU counts per scenario) are supported via the MaxoPerf API. See the API reference for the scenarios payload field.

---

Test detail: Overview

After opening a test, the Overview tab (the default view) shows aggregated run history for this test definition.

Test detail — Overview tab: four charts summarising run history for this test. Use these to spot performance regressions across runs.

The Overview tab shows four charts:

Chart	What it shows
Duration trend	Run duration (seconds) over time — a time-series line per recent run
Status breakdown	Count of passed, failed, and other statuses across runs
Last run — RPS trend	Requests-per-second sample from the most recent run
Health snapshot	Health indicator bars from the most recent run

The test name is shown at the top of the page as an inline-editable title — click it to rename the test. The Run test / Run VarioTest button at the top right launches a new run from this definition.

How to use the Overview tab

1. Open a test from the list, or navigate directly to /tests/<testId>/overview.
2. Read the Duration trend chart to spot runs that took significantly longer than usual.
3. Read the Status breakdown chart to see the proportion of passing vs. failing runs.
4. Click Run test to start a new run. A confirmation dialog opens asking whether to open the run detail immediately or stay on the test.

---

Test detail: Configuration

The Configuration tab lets you edit the test’s project assignment, load profile, location plan, failure criteria, and verdict mode. Changes apply to future runs; existing run configuration snapshots stay immutable.

Test detail — Configuration tab: all editable test settings. Scroll through sections and click Save configuration when done.

Sections on this tab:

Test details — Change the project this test belongs to. The detected engine is shown read-only (controlled by files).

Scenario and files — (Single tests only) Upload new files, change file roles, revalidate, or delete files using the same drag-and-drop panel as the New test wizard.

Scenarios — (VarioTests only) A read-only table of the scenario tests in position order.

Load configuration — Edit total virtual users, max VUs per runner, ramp-up duration, stop mode, and duration / iterations. The same sliders and inputs as New test.

Locations and capacity — Add, edit, or remove location rows. The auto-balance button is available here too.

Failure criteria — Define SLA gates: select a metric (e.g. p95 latency, error rate), a comparator, and a threshold value. When a criterion is breached during a run, the run is marked failed. Multiple criteria can be added.

Verdict mode — Choose how a multi-runner run is judged when failure criteria are defined: either (any runner breach fails the run), all (all runners must breach), or combined with an early-stop option.

How to update a test configuration

1. Navigate to the Configuration tab on the test detail page.
2. Edit any section — changes are held locally until you save.
3. Click Save configuration in the sticky footer bar.

Edit permissions

The Save configuration button is disabled if your role does not have edit access to the test. Contact your workspace admin to request write access.

---

Test detail: Runs

The Runs tab shows the recent run history for this test definition.

Test detail — Runs tab: run history for this test. Click any run name to open the run detail page.

The table has columns: Run (name, clickable link to run detail), Status (badge), Duration (seconds), and Started (your local timezone).

How to use the Runs tab

1. Open the Runs tab on any test.
2. Click a run name to go to that run’s detail page.
3. If the table is empty, no runs have been created for this test yet — click Run test on any tab to start one.

---

Test detail: Schedules

The Schedules tab manages recurring scheduled runs for this test.

Test detail — Schedules tab: create and manage recurring scheduled runs using cron expressions.

Schedules are defined with a cron expression and an optional display name. Each schedule shows its status (active / paused), the cron expression, and the next scheduled run time in UTC.

How to add a schedule

1. Open the Schedules tab on a test.
2. Click Add schedule.
3. Enter a cron expression (e.g. 0 8 * * 1-5 for 08:00 Monday–Friday UTC).
4. Optionally give it a display name.
5. Click Save. The schedule appears in the list and the next run time is shown.

Pause without deleting

Use the pause toggle on any schedule row to temporarily suspend it without losing the cron configuration. Resume it when you are ready to run again.

For a full walkthrough, see Schedule recurring tests.

---

Test detail: Files

The Files tab provides a dedicated view for managing the test’s scenario and supporting files outside the full Configuration form.

Test detail — Files tab: upload, revalidate, reassign roles, and download test files without opening the full Configuration tab.

The Files tab shows the same drag-and-drop authoring panel as the Configuration tab’s Scenario and files section, but dedicated to this task. For each file you can:

• Download — download the original file without exposing a presigned URL.
• Set as entrypoint — mark a file as the primary scenario entrypoint.
• Revalidate — request a fresh engine detection pass on the file.
• Delete — remove the file from the test.

VarioTest files

VarioTests do not own files directly — each constituent scenario test owns its own files. If the active test is a VarioTest, the Files tab shows a message directing you to open each scenario test to manage its files.

For a full walkthrough of file management, see Upload test files.

---

Test detail: Data

The Data tab controls which workspace secrets are injected into this test’s run environment.

Test detail — Data tab: bind workspace secrets to this test. Checked secrets are injected as environment variables when the test runs. Secret values are never shown.

The tab lists every secret in the test’s workspace. For each secret you can:

• Check the inject toggle — mark the secret to be injected as an environment variable when this test runs.
• Set an env-name alias — override the default environment variable name (useful when your script expects a specific env var name that differs from the secret’s name in the console).

Click Save bindings to persist the selection. Secret values are never shown in the console.

How to bind a secret to a test

1. Open the Data tab on a test.
2. Ensure the workspace has at least one secret (create secrets via Secrets in the sidebar — see Manage test secrets).
3. Check the Inject checkbox next to each secret you want available to the test script.
4. Optionally set a custom Env name to override the default variable name.
5. Click Save bindings.

VarioTest secret bindings

VarioTests do not own workspace secret bindings directly. Configure secret injection on each individual scenario test instead.

---

Tips & gotchas

• Engine is read-only after creation. The detected engine is determined by the scenario file format and cannot be changed manually. To switch engines, upload a file of the new type and delete the old one — the engine re-detects automatically.
• Load profile edits apply to future runs only. Changing total VUs or duration on the Configuration tab does not affect runs that have already started. Each run captures an immutable configuration snapshot.
• Failure criteria trigger early stop. When a criterion is breached, the run can optionally stop all runners early (controlled by the Verdict mode → Combined early stop toggle on Configuration).
• Renaming a test is safe. The test id is permanent and never changes; the display name can be edited inline on the list or via the inline title on the detail page.
• VarioTest scenario order matters. Scenarios run in listed order by default. Reorder in the New VarioTest Review step — you cannot reorder after creation without recreating the VarioTest.
• Workspace secrets must exist before binding. If the Data tab shows “No secrets in this workspace yet”, navigate to the Secrets section to create them first.

---

Related docs

• Tests and runs — explains what a test and a run are, and how they relate.
• Engines — Taurus, JMeter, k6 — supported test engines and file formats.
• Scenarios and VarioTest — deep dive into VarioTest composite runs.
• Run your first test — end-to-end walkthrough: create a test, run it, check the results.
• Upload test files — file roles, engine detection, revalidation.
• Manage test secrets — creating secrets and binding them to tests.
• Schedule recurring tests — cron-based scheduling for automated runs.
• Runs — read results — interpreting run results after a test completes.