Test a journey that spans UI, API and data
A workflow chains steps with shared context, then checks that the UI, the API and the stored value all agree.
What it tests
- A workflow is an ordered list of steps with shared context variables.
- Steps can be UI actions, API calls, read-only state checks, wait-for-condition and assertions.
- Build a workflow from plain English, from approved flows, or from a manual definition.
- Check end-state invariants after the last step, such as the order, payment and inventory agreeing.
- Check cross-layer consistency: a value in the UI equals the API response and the stored value.
- Repeat a step or run it in parallel to detect idempotency and race problems.
How a run goes
- Step 1
Lay out the steps
Describe the journey in plain English or build it from approved flows.
- Step 2
Set the invariants
State what must be true at the end, drafted from plain English for you to confirm.
- Step 3
Catch the mismatch
Stakari reports where the UI, API and stored value disagree.
Coming soon
- Webhook triggers, received from the app under test or sent by Stakari.
- Branching, failure injection through mocks, and email checks.
Explore the other modules
- Web app testingDrive your app in a real browser, one isolated session per role.
- API testingPostman or OpenAPI: contracts, bad input, auth, idempotency, concurrency.
- Multi-role & multi-tenantCheck the access matrix and try to cross between tenants.
- AI agent testingMulti-turn attacks with canary and state oracles.