Skip to content

load testing

Run artifacts

Run artifacts are the files a performance run needs or produces, such as scenario bundles, logs, result exports, manifests, and reports.

Also known as: test artifacts, result artifacts

Definition

Run artifacts are the inputs and outputs tied to a performance run: uploaded scenario files, generated execution bundles, logs, manifests, exports, and reports.

In Maxoperf

Maxoperf keeps test files, bundles, logs, and result views connected to the run so teams can reproduce what happened and compare later runs without hunting through runner disks.

Common pitfalls

  • Storing credentials in scenario files.
  • Deleting logs before the team has explained a failed run.

FAQ

Why keep run artifacts after a test?

Artifacts make a run explainable later: which files were executed, what logs were captured, and what result data backed the release decision.

Should secrets be stored in run artifacts?

No. Runtime secrets should be injected through a secret workflow, not committed into scenario files or result bundles.