Changelog

When the report directory sat on a different filesystem from where artifacts were written (a Docker volume mount, a RAM disk, or a Windows temp folder on another drive), screenshots, videos and other artifacts could go missing from the report, leaving only a "Failed to move file" line behind. They're now copied across as intended.

Fixed in @testrelic/playwright-analytics 2.16.3, @testrelic/appium-analytics 1.2.2 and @testrelic/maestro-analytics 1.4.2. The latest releases are 2.16.4, 1.2.3 and 1.4.3.

Four things every Maestro run already captured never appeared in the report. They do now.

• Replay. The screen recording with a scrubber marked once per step; clicking a step seeks the video.
• Driver log. maestro.log was never rendered in the report at all. It has a Driver log tab, with each line's source, tag, pid and stack trace.
• The device. The device a run ran on never reached the report. It now opens with a device strip, and flow rows carry a device badge. The platform is a field of its own, so it is no longer appended to your tag list.
• Step kinds. Ten kinds of Maestro step all rendered as one of four badges, so AI and DEV steps never showed a badge of their own. Steps are badged by kind now.

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

Screenshots and AI defects are now scoped to the flow they belong to; every flow used to show the whole run's screenshots.

Released as @testrelic/maestro-analytics 1.4.0. The report schema moves to 1.1.0 — every addition is optional.

Fixed an issue where some mobile test runs and Maestro flow runs could fail to upload or show missing details in the Test Runs feed.