Skip to content

Updated May 14, 2026

Upload test files

Bring Taurus, JMeter, or k6 assets into Maxoperf with clear entrypoints, supporting files, and secret-safe runtime configuration.

Before you start

  • Existing Taurus, JMeter, or k6 files.
  • A project where the test should live.

Identify the entrypoint

The entrypoint is the file Maxoperf should execute. For existing assets, make this explicit: Taurus YAML, direct JMeter JMX, or k6 script.

Upload referenced assets

If the entrypoint references data files, included configs, helper scripts, or certificates, attach them to the same test so the run bundle is reproducible.

Keep secrets out of artifacts

Do not store API keys or passwords in scenario files. Use the product’s secret-binding workflow so runtime values are injected for the run without appearing in public content, committed files, or result pages.

FAQ

Can one test include supporting files?

Yes. Keep the entrypoint clear and attach referenced assets so the run bundle is complete.