Automation

An automated case is a list of steps a real browser carries out, with checkpoints where you say — in plain language — what should be true. No selectors in your test code, and no assertions to write.

The shape of a project

Before your first case, three things are worth setting up:

1. An environment — where the app lives, and the values that differ per environment.
2. Variables — values shared by every case, including encrypted secrets.
3. An app adapter — the elements you point at often, named once.

Then you write blocks (reusable steps), cases, and group them into flows.

What a run costs

Only the AI is metered. A checkpoint is 1 credit, a question about the screen is 1, a Do step is 3 however many tries it takes, and a checkpoint that reads a PDF is 2. Everything else — clicks, fills, waits, backend calls, video, traces — is free.

Pages

• Setting up — environments, variables, adapters, fixtures
• Writing a test case — every step kind
• Checkpoints and Do steps — the two that use AI
• Blocks and flows
• Running and reading a run
• The AI judge