Skip to content

docs: document flows - #248

Closed
jsfez wants to merge 1 commit into
mainfrom
jeremy/flows-documentation
Closed

jsfez wants to merge 1 commit into
mainfrom
jeremy/flows-documentation

Conversation

@jsfez

@jsfez jsfez commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Documents the flows feature: how Argos derives a journey from your test structure, steps versus variants, the Flows tab, and what changes in the build review.

Depends on the app feature shipping (argos-ci/argos#2441) and on the SDKs recording the capture order (argos-ci/argos-javascript#360) — the step-order section describes that behaviour.

🤖 Generated with Claude Code

Flows group the screenshots a test captures into the journey they walk,
so a change is reviewed with the screen before and after it in sight.
The page covers how a flow is derived, steps versus variants, the Flows
tab, and what changes in the build review.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jsfez

jsfez commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

Closing: the Flows tab and the flow page never shipped. The five flows PRs were closed in August in favour of ingesting the Playwright test report first, and building flows on top of it later. The review-side half that did ship is documented in #256.

@jsfez jsfez closed this Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant