Upload test files

Maxoperf accepts the test files your team already runs locally. Mark the entrypoint, the one file that starts the test, and upload its supporting files with it.

1. 0:12 JMeter JMX
2. 1:48 JMX with a CSV data file
3. 2:45 Playwright script
4. 3:38 k6 script
5. 4:29 Python (apiritif) / Locust / Gatling
6. 5:04 Change load mid-run

Upload test files.

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.

To choose an 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. Include every data file, helper module or include that 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 the 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 in a test file. Maxoperf logs file content as part of the run bundle. Use Manage test secrets instead. Maxoperf injects those values at run start, and they 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. Finished runs keep the file set they used, so you can change a test without changing past results.

Where to go next

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