journey

Replays each walkthrough and records it.

Reference

Runs
your installed Chrome against your dev server
Ships as
off; a warning once on
Needs
walkthroughs turned on, Node 20, Chrome

How it works

A journey is a short list of things a person does in your app, in plain sentences, with what should be true after each one. The builder writes one for each change you can see, and works out the exact click or check for every sentence against the running app.

This check replays those journeys and records every step: a screenshot with the clicked element outlined, whether each expectation held, and the changed lines of code behind the step. A failing step is named, with what the page showed instead.

If the app will not start or Chrome is missing, it reports that it could not run. That never counts as a pass.

/hyperpower:init turns it on when you say yes to walkthroughs. It warns at first. Make it stop runs once your replays are steady:

gates:
  journey: { enabled: true, blocking: true }