Changelog

What shipped recently in Appium SDK.

September 2026


Appium SDK·

The Appium report now shows what it was already capturing

Four things were captured on every run and never reached the report. They are in it now.

  • The device. The report showed you two facts about the device — android · native. There is now a device strip: OS and version, device name, driver, app under test, native or webview mode, UDID. Rows and the detail header wear a device badge. The platform has a field of its own now, so it is no longer appended to your own tag list.
  • Step categories. A swipe, an app launch, a keypress and a screenshot all rendered as the same badge. Steps are badged by kind now, and the run is broken down by it. The cloud timeline and Ask AI filters are unchanged.
  • Device-log provenance. A crash-log line used to be indistinguishable from ordinary logcat chatter. Each line now keeps its tag, source, pid and stack trace, and shows them.
  • Every screenshot, not just the first. One screenshot per failure has always been captured, but only one reached the report. All of them are kept in capture order and rendered as a strip.

There is also a Replay view — the screen recording with a scrubber marked once per step, where clicking a step seeks the video — and the shared run-level layout: a verdict band, tiles for what this run actually captured, and a needs-attention block that leads with the failing step and the device-log line recorded beside it.

Two attribution fixes: screenshots are scoped per test, and AI defects belong to the flow they were found in rather than to the run. Network entries stop claiming every request is xhr and derive a resource type from the response MIME type.

Released as @testrelic/appium-analytics 1.2.0. The report schema moves to 1.1.0 — every addition is optional, so anything reading 1.0.0 keeps working.