--wait, the command polls until completion and exits non-zero on failure.
Usage
--test-plan or one or more --test-case flags - not both.
Options
| Flag | Short | Description |
|---|---|---|
--test-plan <id> | -t | Test plan short ID (e.g. pln_abc123) |
--test-case <id> | -c | Test case UUID (repeatable) |
--application-overrides <json> | JSON array of application overrides - point apps at custom URLs, environments, or builds | |
--wait | -w | Poll until the run finishes, then print results |
--poll-interval <secs> | How often to check status when waiting (default: 5) | |
--timeout <secs> | Max time to wait before giving up (default: 600) | |
--json | -j | Machine-readable output. Progress goes to stderr. |
--api-key <key> | Per-command API key override | |
--help | -h | Show command help |
Behavior
- Without
--wait- prints the run short ID and exits immediately. - With
--wait- polls untilCOMPLETED,ERROR, orCANCELLED, then prints results. - Exit code is
1if any test case ends asFAILED,0otherwise. - With
--wait --json, progress logs go to stderr so stdout stays clean JSON.
Examples
Application overrides
--application-overrides redirects one or more applications to a different URL, saved environment, or build for this run. Same JSON shape as qatech chat --application-overrides - useful for testing preview deployments, tunnels from qatech tunnel, or any URL not configured as a saved environment.
environment object accepts any of:
| Form | When to use |
|---|---|
{"url": "..."} | Inline URL override (tunnel, preview, etc.) |
{"shortId": "env_xxx"} | Reuse a saved environment |
{"applicationBuildShortId": "bld_xxx"} | Pin to a specific build |
JSON output
The shape returned byqatech run --wait --json matches qatech status --json:
result-"PASSED" | "FAILED" | "SKIPPED" | nullrunTestCases[].resultTitle- human-readable failure reason (nullif passed)runTestCases[].evaluationThought- agent’s reasoning about the result