Create Workflow Test Run
Create a workflow-scoped test run.
workflow_id is the execution context. Optional scope narrows the
run to one saved test or one block; omitted scope runs all workflow tests.
workflow_id in the request body and
optionally narrow execution with scope. If scope is omitted, every saved
test in the workflow runs.
The response is a run resource. Use its id with the run-id-first endpoints:
Get Workflow Test Run, List Test
Run Results.
The request body has a workflow context and an optional scope:
- omitted
scope- run every saved test in the workflow. scope.type = "single"- run one saved test bytest_id.scope.type = "block"- run every saved test for one block byblock_id.
Authorizations
Body
Create a workflow test run. Provide a workflow_id, and optionally narrow execution with scope to a single test or one block. Omit scope to run every saved workflow test.
Response
Successful Response
A batch execution of a workflow's tests, with overall lifecycle, timing, and pass/fail counts.
Public summary of what started a run: just the trigger category.
The full per-variant detail (schedule_id, parent_run_id, sender, ...) is
kept internally on StoredWorkflowRun.trigger but intentionally not
exposed in the public API surface.
The test run has been created but execution has not started.
- PendingWorkflowTestRun
- QueuedWorkflowTestRun
- RunningWorkflowTestRun
- CompletedWorkflowTestRun
- ErrorWorkflowTestRun
- CancelledWorkflowTestRun
Public workflow-test target.
The storage layer remains block-scoped today, but the API shape names the tested entity explicitly so workflow-level targets can be added later.
Aggregate counts for a batch of block-test runs.
Each individual run contributes to exactly one lifecycle_counts
bucket, and additionally to one outcome bucket when
lifecycle_counts.completed is incremented.