Skip to main content
Write a conversation once, run it against any agent, and get a Pass or Fail verdict with the judge’s reasoning. Tests live in a shared workspace library, run against your agent’s current draft, and never touch what’s published — so you can iterate on a prompt and re-run in seconds.

​
How a test works

A Single Turn test hands your agent a scripted conversation and asks it to produce the next reply:
  1. You script a conversation history of agent and user messages.
  2. The agent generates the next reply using its current draft configuration and the same language model that answers in live conversations.
  3. An LLM judge scores the reply against your Expectation, optionally calibrated by success and failure examples, and returns a verdict with its reasoning.
Tests run as text — no audio is synthesized — but the agent uses its full draft configuration: the knowledge base is consulted, and the agent can invoke its attached tools while generating the reply. Webhook tools send real HTTP requests during a test, so point them at a staging endpoint. For end-to-end verification with voice, use preview calls.

​
Create a test

Tests are workspace-level resources, managed under Library → Tests in the console and shareable across every agent in your workspace.
1

Start a new test

Open Library → Tests and click New test. Give it a name and keep the type as Single Turn.
2

Script the conversation

Under Conversation, click Add message to build the history the agent sees — each message is either an Agent or User turn. When the test runs, the agent generates the reply that comes next.
3

Define the judging criteria

Under Judging, write the Expectation — what a correct reply must do. Optionally click Add example to provide success and failure examples; they calibrate the judge but aren’t required.
4

Save

Click Save. The test is now in your library, ready to attach to agents.
The type picker also offers Tool tests, available today, which check whether the agent called a specific tool. Multi Turn tests are coming soon.

​
Attach tests to agents

A test only runs against agents it’s attached to. Attach from either side:
  • From the library — open the test’s Access tab and toggle it on for each agent.
  • From the Builder — on the agent’s Tests page, click Add tests and pick from the library.
One test can be attached to many agents, and each agent keeps its own last result. Remove from agent detaches the test from that agent only; Delete in the library removes the test from all agents.

​
Run a single test

Open the test and switch to its Run tab. Pick an agent that has access, then click Run test. The verdict card shows: If the run can’t complete, the verdict shows Error with the error message in place of the reply and reasoning.

​
Run every test for an agent

On the agent’s Tests page in the Builder, click Run all. Each row moves through queued → running → Pass/Fail — or Error if a run can’t complete — and the page header summarizes the latest batch — for example, 4 passed, 1 failed on last run. Use the row menu to re-run a single test, edit it, or remove it from the agent.

​
Tests run against the draft

Tests always exercise the agent’s latest draft configuration — including unpublished changes to the system prompt. That makes the loop fast:
1

Edit the draft

Change the system prompt or first message in Configuration.
2

Re-run

Click Run all — no publish needed.
3

Publish when green

Once results look right, publish the draft. Running tests never publishes anything and doesn’t affect your agent’s publish state.

​
Limits

​
Going further

Preview calls

Talk to your draft agent live, with voice, tools, and transcripts.

Versions & publishing

How drafts become immutable published versions.

Configuration

System prompt, first message, and everything tests exercise.

Core concepts

Agents, drafts, sessions, and the workspace library model.