Skip to content
OttoTester docs

Read a run report

The run detail

Section titled “The run detail”

Open a run from the run list to see its report. At the top: the run’s overall status, how long it took, and a summary count — passed, failed, skipped. Below that, a row per test.

Each test row shows its status:

  • passed — the test ran and every check held.
  • failed — the test ran and a check failed.
  • skipped — the test didn’t run, often because something it depended on failed first.
  • running / pending — still going, or not started yet.

Healing isn’t a per-test status. It’s a phase of the run as a whole — if the run went through a healing phase, the healer took a pass at the failures before the report was finalized.

Drill into a failure

Section titled “Drill into a failure”

To find out why a test failed:

  1. Open the failed test from the report.
  2. Walk its steps — each action and check, in order — down to the one that broke.
  3. Open that test’s Playwright HTML report.

Read the Playwright trace

Section titled “Read the Playwright trace”

The Playwright report is the detailed record: every step, a screenshot of the page at each action, the network activity, and the console. For a failed test it includes a trace you can step through — scrub back and forth and see exactly what the page looked like when the script expected one thing and found another.

That’s almost always where the answer is: the script thought it was clicking X; the trace shows what was actually on screen.

Fix it from here

Section titled “Fix it from here”

Once you know what broke, head to Fix a failing test — it covers the healer’s attempt log and the three ways to get back to green.

Section titled “Related”