TestRelic for Maestro

TestRelic adds observability around Maestro flow runs: capture results, artifacts, and sync with the TestRelic cloud when configured.

What gets captured (v1.4.0)

• Per-step detail — per-step timing and per-step parameters (text typed, swipe direction, lat/lon), retry/repeat grouping, and assertions, parsed from the Maestro commands-*.json files.
• Mobile network capture — optional traffic capture via --capture-network (spawns mitmproxy; needs mitmdump on PATH) or by importing a HAR with --har-path ./run.har.
• Device and platform — surfaced in the report, not just in the cloud payload. The platform has a field of its own now, so it is no longer appended to your tag list.
• Step kinds — all ten Maestro step categories badged separately rather than flattened to four, including the AI and DEV badges the renderer previously could not reach.
• The driver log — maestro.log was uploaded to the cloud and never rendered locally. It has a Driver log tab, each line with its source, tag, pid and stack trace.

What the report shows

The overview opens with a verdict band saying what broke, then tiles for what this run actually captured, then a needs-attention block that leads with the failing step and the driver-log line recorded beside it.

Each flow gains a Replay view — the screen recording with a scrubber marked once per step, where clicking a step seeks the video. videoOffset was already being computed in seconds for cloud video sync; the local report now reads it.

Screenshots and AI defects are scoped to the flow they belong to. The Screenshots tab previously took no flow argument, so it showed the whole run's screenshots on every flow.

Next steps

• Get Started with Maestro
• Maestro Cloud Quickstart