Attach and run tests

Attach tests to the Agent configuration to make the intended regression suite visible in Agent Studio. Tests can be attached at the Agent level or to an existing Workflow node. An attachment stores a small reference; the invocation freezes the actual test revision and Agent configuration.

Attach to Main#

Agent Testing execution is scoped to Main. Attach a visible test from the Tests section, optionally select a Workflow node, and save the Agent draft. Creating a test can attach it atomically so a failed save does not leave a partial attachment. A missing node or insufficient test permission is rejected before the draft changes.

Deleting a test removes its references from mutable drafts. Published versions and past invocation snapshots are immutable and are not rewritten.

Select tests and target#

Run one selection, all attached tests, or a folder. Folder expansion and ordering are frozen before repeats are created. Choose Draft to evaluate the current user's executable Main draft, or Live to evaluate Main's published production version. The target is never inferred from an old result.

Dashboard repeat choices are 1, 3, 5, and 15. The API accepts 1 to 50 repeats. Repeats generate separate runs so intermittent behavior appears in the pass rate and failure grouping.

Pass preflight#

A request can include 1 to 5,000 expanded entries. Preflight verifies workspace membership, visibility, attachment and Workflow-node consistency, target availability, Tool and Procedure references, workspace activation, and quota. Failure before persistence creates no partial invocation.

The service snapshots Agent configuration, test revisions, display names, folder paths, and Tool definitions before enqueueing work. To understand safe Tool execution, read Tool Invocation and mocks. To inspect the asynchronous result, continue to Past runs and results.