Create Workflow Test
Create a workflow test.
Pins an expected outcome for one block in a workflow. Provide the
workflow_id, the target block, an assertion describing the expected
output, and a source of test inputs (explicit handle inputs or a capture
from a prior run/step). Returns the created test with status 201.
workflow_id in the request body.
The request body has three parts:
target— the block the test runs against.source— where the inputs come from.manualcarries an explicithandle_inputsmap;run_stepreferences a previous workflow run plus the optional step inside it whose inputs to capture.assertion— required. One assertion per test against one declared output handle (see Workflow Tests for the assertion shape and the available operators).
Authorizations
Body
Body to create a workflow test: the target block, an input source, and an assertion to evaluate its output.
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.
- ManualWorkflowTestSource
- RunStepWorkflowTestSource
Block-test assertion against one declared output handle.
target is the only supported shape: an output handle id and an
optional relative path inside that handle's payload.
Response
Successful Response
A saved workflow test: a target block, an input source, and the assertion evaluated against its output.
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.
- ManualWorkflowTestSource
- RunStepWorkflowTestSource
Block-test assertion against one declared output handle.
target is the only supported shape: an output handle id and an
optional relative path inside that handle's payload.
Single-rule schema dependency for Level 2 drift detection.
valid, drifted, broken none, partial, drifted, unknown Summary of the most recent block-test run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
Summary of the most recent block-test run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
Summary of the most recent block-test run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
When the workflow test was created
When the workflow test was last updated