Back to corpus
research noteexperiment writeup candidatescore 26

Flow Walker — E2E Flow Testing Pipeline

This skill teaches you how to use flow-walker to execute E2E flows on the Omi Flutter app, verify results, and publish shareable HTML reports. flow-walker is an agent-first testing CLI that works with agent-flutter (Marionette) for UI interaction.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

--- name: flow-walker-pipeline description: "How to use flow-walker to run, verify, and publish E2E flow reports for the Omi Flutter app. Covers the full pipeline from YAML flow definition to published HTML report with screenshots and real timestamps." allowed-tools: Bash, Read, Glob, Grep --- This skill teaches you how to use flow-walker to execute E2E flows on the Omi Flutter app, verify results, and publish shareable HTML reports. flow-walker is an agent-first testing CLI that works with agent-flutter (Marionette) for UI interaction. Flows live in `app/e2e/flows/<name>.yaml`. Each flow defines a sequence of steps with expectations. | Kind | Fields | Meaning | |------|--------|---------| | `text_visible` | `values: [...]` | All listed strings must appear on screen | | `interactive_count` | `min: N` | At least N interactive widgets visible | **Replay mode:** If a `.snapshot.json` exists for the flow, `record init` returns a replay plan with cached coordinates. Check `replay.mode` — if `"replay"`, use `replay.steps[id].center` coordinates for cached steps.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.