QUqualgent
test-runs

Get the resolved test plan (with setup/act/verify kinds) for a test run

Return the ordered plan steps that this run was queued against, with QUA-2144 [setup|act|verify] kind tags surfaced as a structured field.

Variables (e.g. `{{username}}`) are already resolved — the strings here
are exactly what the agent saw. Pairs with `GET /v1/test-runs/{id}/steps`:
that endpoint says *what the agent did*, this one says *what it was
supposed to do and how each step was categorized*.

**Path Parameters:**
- `test_run_id`: The unique identifier of the test run

**Returns:**
- Ordered array of plan step objects (`step_number`, `kind`, `description`).
- Empty array if no plan is recoverable (e.g. legacy runs with neither
  `resolved_steps` nor a pinned test_case_version).

**Authorization:**
- Only returns plans for test runs belonging to your organization.
get/v1/test-runs/{test_run_id}/plan

Request

Path parameters

test_run_idstring required

Headers

x-api-keystring

Response

Successfully retrieved test run plan

step_numberinteger required

1-indexed position in the plan

kind'setup' | 'act' | 'verify' nullable

Step category from the QUA-2144 [setup|act|verify] tag. Null when the author didn't tag the step (intentionally distinct from "act" so downstream classifiers can tell the cases apart).

descriptionstring required

Step description with variables resolved.

Example response

[
  {
    "step_number": 1,
    "kind": "setup",
    "description": "Open the app"
  }
]

Changes

No recorded changes to this operation across all 3 revisions of this API.