sakioriFailures and likely causes
Red doesn’t just mean red. When a step fails, Sakiori gives the likely cause in plain terms:
| Likely cause | What it means |
|---|---|
| Real bug | The app isn’t doing what the recording saw it do. |
| UI change | The page changed in a way Sakiori couldn’t confidently repair. |
| Timing | Something didn’t appear in time. |
| Test data | The data the test used was the problem. |
| Environment | The environment itself wasn’t working. |
The evidence
Each failure shows what the cause is based on:
- whether the element was found,
- failed network requests,
- the text that never appeared,
- how the page changed,
- a screenshot from the moment it failed.
“Needs your call”
When the evidence doesn’t point clearly to one cause, the failure is marked needs your call instead of being guessed.
Can it heal around a real bug?
That’s what it’s designed to avoid. A dead button or a server error stops the run and is reported with a likely cause, because the step no longer produces what the recording saw happen.
Reading a long run
A step map shows every step at a glance, coloured by result. Routine steps fold away, and the run opens at the step that stopped. Press J or K to jump between the steps that need attention.