Documentation

From an empty screen to a flow that runs, in four steps.

Frontmatter, prose and executable step blocks.

What every part of the screen does.

Any frontmatter property you like, editable from the document.

A folder of flows as a table you can sort, filter and search.

Every key you can use inside a step block.

Where the callable methods come from, and how they document themselves.

Flow memory: what one step writes, the next one reads.

Assert the status and the body, including JavaScript expressions.

Assert on messages produced asynchronously, out of band.

Fake what a dependency answers, so you can test locally.

The little expression language behind views.

Every {{ template }} you can use in a flow — random data, dates, ids.

Your context folder: flows, applications, credentials.

Generate a flow from a description, or rewrite one with the magic wand.

Link a flow to a Test issue, and pull the tests of a project.

Drive a web application from a flow. Experimental.

One env file per application per environment — nothing in the repo.

What happens when you press Run, and how to read the results.

Run flows headlessly — the CI/CD side of the tool.

The things that usually go wrong, and what to check first.

Exactly which network calls the tool makes, and when.

Docs, source and issues.