Every flow you have tested, per project

Runs tell you what happened on one visit. Flows tell you what your tests cover across all of them, so you can see the gaps before a user finds them.

• Read from your reports. Every run on the project is read, however old, and every check that tests something is placed in a flow: sign up, log in, search, forms, cart and checkout, navigation and links, layout on devices, theme, accessibility, console and network errors, or a flow of its own when it is specific to your app. Bookkeeping checks are left out: device coverage, screenshots captured and timed waits. A run that ended before reporting checks is read from its steps.
• Last result first. Each flow shows its latest verdict, a tick per run, when it was last tested, its checks and findings from that run, and the failures in the last 30 days. Failing flows sit at the top. A run that was blocked before it could test the flow shows as blocked, not as a failure, and a run that stopped before reporting any checks says so instead of inventing one.
• What has gone quiet. Flows not tested in 14 days are marked stale and counted at the top of the page.
• What nobody tested. The common flows no run on the project has tested are listed with a Test it button that opens New test with a mission for that flow.

Open it from Projects, then Flows on any project. Nothing is estimated: a flow appears only after a run tested it.