CLI Arguments
CLI arguments let you change a run at launch time without editing code. They are useful for CI, containers, and reusable test hosts.
Matching docs
Search across docs titles, summaries, groups, and section headings.
Use Up and Down Arrow to move through results, then press Enter to open the active page.
No indexed docs matched that search. Try a broader term or open the docs hub.
What this page helps you do
What this page helps you do
CLI arguments let you change a run at launch time without editing code. They are useful for CI, containers, and reusable test hosts.
Who this is for
Engineers writing or reviewing scenario code in one of the supported SDKs.
Prerequisites
- A scenario or runtime surface you want to wire correctly in code
By the end
The exact SDK surface you need for this part of the runtime.
Use this page when
Use this reference when you already know the workflow and need the exact CLI Arguments API surface in code.
Visual guide
Guide
Format
Use only `--key=value` syntax. Arguments without `--` are ignored, boolean options use strict true or false parsing, and key-only flags do not imply true. Enum-like keys use strict token parsing: NodeType supports Single, SingleNode, Coordinator, and Agent, or numeric 0, 1, and 2. ReportFormats accepts only txt, html, csv, md, or the markdown alias. Examples include `--testsuite=orders`, `--reportformats=html,csv`, `--nodetype=coordinator`, and `--runnerkey=rkl_xxx`.
Supported Arguments
Common keys cover config and infraconfig paths, suite and session naming, report options, node and cluster settings, scenario targeting, logging, restart attempts, and licensing. Pass them to the executable, script, or container command that launches the scenario host.
When To Use
CLI arguments are most useful when the same test host should run in multiple environments without code changes, such as CI pipelines, container jobs, or shared runtime images.
SDK reference samples
Use these SDK samples to compare how CLI Arguments is exposed across the supported languages before you wire it into a full scenario.
If you run these examples locally, add a valid runner key before execution starts. Set it with WithRunnerKey("...") or the config key LoadStrike:RunnerKey.
CLI Run Example
using LoadStrike;
<your-loadstrike-test-command> --testsuite=smoke --testname=orders-http-to-kafka --targetscenarios=orders-http-to-kafka --reportfolder=./reports --reportformats=html,csv --runnerkey=rkl_your_local_runner_keySupported CLI arguments
Load normal runtime config or infra config from a JSON file before the run starts.
Override run identity values for one execution without changing the code.
Control local report output and output formats. reportformats uses the same comma-delimited format tokens as JSON config.
Positive millisecond values for realtime reporting cadence and timeout behavior.
Cluster role and transport overrides for one execution.
Comma-delimited scenario filters that change which scenarios run on which roles.
Logging and runtime behavior overrides. Boolean values must be explicit true or false.
Set the runner key and the license-validation timeout for the current run only.
Arguments must use the --key=value form. Key matching is case-insensitive and values are not inferred from key-only flags.