Legacy tests

Tests you built with the visual builder are now Legacy tests. They keep running for now, but will be archived in future.

What changed

Buildprint tests are now files your agent writes and runs from the CLI. The visual builder, its test groups, and its run history moved under Tests > Legacy tests. Old links redirect there.

How this improves the tests feature

This means that agents can more easily write tests for you. It also makes them run much faster, more reliably, and do not require much agent intervention, which would eat up your token usage.

What still works

• Edit an existing legacy test in the builder.

• Run a legacy test or group from the app.

• View legacy run history.

• Existing deploy automations that run legacy tests keep firing.

What is blocked

• New legacy tests and new groups.

• Creating or updating legacy tests through the API or MCP tools. The tests endpoints are no longer in the public API reference.

• Adding Run tests to a new automation.

What to do

Ask your agent to rebuild the tests you still need as files. Delete legacy tests you no longer run.