The interactive panel connects each authored action to the rendered terminal state. Choose the intentional failure to inspect the exact mismatch captured from the repository fixture. Presentation timing is illustrative; it is not a performance measurement.
Interactive example · recorded terminal statesPaused
examples/menu.json
1{
2 "steps": [
3 {"expect": "> Deploy preview"},
4 {"key": "ArrowDown"},
5 {"expect": "> Run diagnostics"},
6 {"key": "Enter"},
7 {"expect": "all systems healthy."}
8 ]
9}
Rendered screen
$ playtestr test examples/menu.json
PLAYTESTR / mission control
> Deploy preview
Run diagnostics
Exit
Use arrow keys and Enter. Press q to quit.
Playtestr waits until the initial selection is visible.
Step 1 of 6
Fixture evidence from the repository; interactive data is loading.
Run the examples locally
The website controls explore prepared, sanitized states. The browser does not run a pseudoterminal. To execute the same repository fixtures, build the current source checkout and run:
go build -o bin/demo ./cmd/demo
go run ./cmd/playtestr test examples/menu.json
go run ./cmd/playtestr test examples/snapshot-mismatch.json
The first command should pass. The snapshot-mismatch command is deliberately expected to exit 1 and write its actual screen and diff. On Windows, add .exe to the demo output name.