Debugging & reports
Inspect live step reports, terminal logs, and shared run reports.
Step reports
Each run produces a live step report: which lines passed, which failed, and why. Failed steps often include enough detail to adjust the wording (label text, scroll direction, waits).
Terminal logs
The built-in terminal shows connection steps, driver output, and run events. Use it when a device will not connect, an app install fails, or a step fails with a low-level error.
Screenshots in reports
Add a screenshot step to capture the current screen into the report — useful for
visual checkpoints and bug reports without asserting anything.
Shared reports
After a run, you can open or share the run report so teammates can review the same step-by-step outcome outside the editor.
Tip: Prefer step-through runs while debugging flaky UI. Fix one failing line, then re-run from there or restart the flow.