Run a test

Start a run

1. Open the test on the Tests page.
2. Pick a connected device in the Run on dropdown (see Devices).
3. Press Run, or use its split menu to run the whole folder or a plan.

What a run does

The agent works in phases: the folder's setup.md first, then the tests, then teardown.md, with rules.md applied throughout. Each phase is one agent execution: read the file, drive the UI, write a report with screenshots. A failing setup records its tests as broken, the entry criteria weren't met.

Watch it live

The conversation is the live test execution log, every message, tool call, and screenshot as it happens. Use it to catch unexpected behaviour before the report exists.

1. Open the Runs page.
2. Pick the run in the runs sidebar on the left, it lists every run of the project, and several runs can be active at once; each streams its own conversation.
3. Follow along, the controls at the top of the conversation:
   • Autofollow: keeps the view pinned to the newest entry while the run streams; scroll up to inspect something and it pauses, click it to snap back.
   • Quiet: just the story: the agent's narration, minimal noise.
   • Detailed: the default: narration plus every tool call with its result, tokens, and latency.
   • Raw: the underlying messages as JSON, for debugging.

Reading the conversation

• Numbered circle + TEST header: one phase (setup, a test case, teardown) with its file path, status badge (PASS/FAIL), and how many tool calls it took, this is where you see each test.
• Text lines: the agent's narration, what it sees on screen and what it decides to do next.
• Chips: tool calls, a screenshot, a keystroke, a click, or a named tool like Save screenshot / Write file, with the result behind it.
• 350 → 26: tokens in → out for that step, the cost signal of the run.
• 500ms: the step's latency.

The same view stays available after the run finishes, see the conversation log on the results page.

After the run: read the report. Recurring runs: Scheduling. Headless / CI: CLI.