Turn runs into insights
Every run an actor completes, whether it's a checklist, an interview round, or a workflow, is recorded in full. This tutorial covers how to read a run report and how to use the insights Stunt Double surfaces on top of it.
Read a run report
A run report is organised into tabs:
- Results, the pass, fail, or error status for each check, with a short explanation for each one.
- Screenshots, the page as the actor saw it at each step, useful for spotting a visual regression that a pass or fail badge wouldn't catch.
- Recording, the full session, step through it in order or watch it play out end to end.
- Knowledge, which knowledge entries the actor drew on for that run, useful for checking whether it's relying on something out of date.
Start with Results to get the headline, then drop into Screenshots or the Recording when a result needs more context than the explanation gives you.
What surfaces automatically as an insight
Not everything worth knowing fits into a pass or fail. As actors work, Stunt Double surfaces insights: notable observations from a run that fall outside strict pass/fail, a confusing step, a broken link, an unexpected result the actor flagged on its own. Insights turn a pile of session recordings into a short list of things worth your attention, without requiring anyone to watch every replay.
Review new insights on a regular cadence rather than only after something breaks; the most useful ones are often things nobody thought to write a check for.
Share findings with your team
Runs and insights are most useful when they reach the people who can act on them. See Integrations for connecting Slack, Linear, and GitHub so failed runs and new insights land where your team already works, instead of waiting to be checked manually.