Upload test files

Maxoperf accepts the same test files your team already runs locally. The important detail is to mark the entrypoint — the one file that actually starts the test — and to upload its supporting files alongside it.

What you can upload

• Taurus YAML (*.yml, *.yaml) — declarative scenarios.
• JMeter scenarios (*.jmx) — exported from JMeter Desktop.
• k6 scripts (*.js, *.ts) — JavaScript or TypeScript modules.
• Supporting files — CSV data, helper scripts, included configs, certificates.

For an explanation of when to pick each engine, see Test engines.

Upload and configure

1. Open the test in the console and switch to the Files tab.

   

   Test detail Files tab — drag files in, mark the entrypoint, and tag supporting files.

2. Drag your files in — including any data files, helper modules, or includes the entrypoint references.

3. Mark the entrypoint. Exactly one file must be the entrypoint. Maxoperf uses that file to choose the test engine and to start execution.

4. Tag any supporting files that the entrypoint references — for example, the CSV the Taurus YAML loads.

5. Save. The console validates the files and shows any unresolved references.

Do not commit secrets

Never put API tokens, passwords, or other secrets directly in a test file. Maxoperf logs file content as part of the run bundle. Use Manage test secrets instead — runtime values are injected at run start and never appear in the uploaded files.

Common file layouts

Engine	Typical layout
Taurus	scenario.yml (entrypoint) + data/users.csv + included YAMLs
JMeter	checkout.jmx (entrypoint) + data/products.csv + plugin scripts
k6	index.js (entrypoint) + lib/*.js helpers + data/*.json fixtures

Updating files

You can re-upload files at any time. New runs use the newest set of files; runs that already finished keep the file set they used. This means you can iterate on a test without rewriting history.

Where to go next

• Test engines — when to pick Taurus, JMeter, or k6.
• Manage test secrets — credentials and tokens.
• Run your first test — launch a run once your files are in.