Create a new workflow test against a single block in the workflow. A workflow test freezes a set of inputs (either captured from a previous run or provided manually) and asserts something about the block’s output the next time it runs. The request body has three parts:Documentation Index
Fetch the complete documentation index at: https://docs.retab.com/llms.txt
Use this file to discover all available pages before exploring further.
target — the block the test runs against.source — where the inputs come from. manual carries an explicit
handle_inputs map; run_step references 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).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.
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.
Successful Response
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.
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