Evidence-Driven Testing

Record proof of behavior and deliver it to the requested destination.

Choose evidence proportional to the change. Use the recorder for interactive flows, scripted captures for headless UI checks, and output pairs for CLI or API changes. Documentation-only edits need content checks and verification of runnable examples, not a recording. Reuse suitable evidence already captured in the task. Publish only to destinations included in the requested work.

The recording is the capture of you testing the app via computer use: start the recorder, then drive the app yourself — click, type, navigate — through each test target. Every action in the video is the test being performed live; the recording has no value as evidence unless it shows that interactive session. If the harness has no computer-use tools but a GUI exists, drive the app with cua-driver instead (see below) — it is still your live session.