Whole journeys, start to finish.
Describe a user journey as structured steps — navigate, fill, click, check — and run it against a staging environment with a dedicated test account.
At a glance
Workflows reuse the browser engine, so every step keeps the same screenshots, assertions and network evidence.
- 01Navigate/sign-inok
- 02FillEmail ← test accountok
- 03FillPassword ← secret ref ••••ok
- 04Clickbutton “Sign in”ok
- ◆CheckpointURL is /dashboardok
- 05Click“New project”writes · approved
- 06AssertProject “QA-run” visibleok
- 07CleanupDelete “QA-run”explicit
01 / Capabilities
What it checks8 itemsWhat it checks.
Everything a run checks, and the evidence it keeps when something fails.
- Registration and login journeysRoadmap
- Dashboard navigationRoadmap
- Create, edit and verify a recordRoadmap
- Form submission with expected outcomeRoadmap
- Search and result checksRoadmap
- Sandbox checkoutRoadmap
- Checkpoints between stepsRoadmap
- Explicit cleanup stepsRoadmap
02 / How it works
Step by step5 stepsDefine the journey
Steps come from a fixed action set: navigate, fill, click, select, assert, wait-for and checkpoint. No free-form scripts.
Mark side effects
Any step that creates or changes data is flagged and needs explicit approval before the workflow can run.
Attach a test account
Use a dedicated account stored as an encrypted credential, scoped to one environment.
Run in staging
Workflows that touch payments, messages or real users don’t run automatically against production.
Clean up
Optional cleanup steps remove what the run created, and are recorded like every other step.
03 / Guardrails
Enforced by the backendNot optionalThe limits come first.
These rules are enforced by the execution backend. The interface can’t switch them off, and neither can an AI.
Structured, not scripted
Workflows are data, validated against a schema — never arbitrary code, AI-written or otherwise.
Approval for writes
Steps that create or modify data can’t run until someone with permission approves them.
Production protection
Journeys that affect real users, payments or records require scoped authorisation and safeguards.
Same evidence
Every step keeps its screenshot, assertion and network record, just like single-page tests.
04 / Questions
End-to-end workflows3 entriesQ.01Can an AI write the workflow?
It can propose steps, but they are translated into the restricted action set and validated before anyone approves them.
Q.02Will it bypass CAPTCHA or MFA?
No. Use test accounts and environments where those are configured for testing.
Q.03When is it available?
It follows database testing.