Skip to main content
Ask AI

Reports

Every run produces an analytics timeline as both JSON and HTML in test-results/. The HTML report is interactive and self-contained; large suites are served from a directory instead. Runs can also be uploaded to the TestRelic cloud, where they open in the Session Workspace.

Interactive HTML report​

For most suites the report is a single self-contained HTML file (analytics-timeline.html) you can open in any browser. Outside of CI it opens automatically when the run finishes (controlled by openReport).

The report includes:

  • Test grid — every test with status, with search and filters.
  • Test drawer — a per-test detail panel.
  • Network DevTools panel — captured requests with method, URL, status, headers, bodies, and timing.
  • Console panel — browser console messages captured per test.
  • Action-step panel — page actions and expect assertions as categorized, video-synced steps.
  • Artifact / video viewer — screenshots and video captured per test from artifacts/, embedded inline.
  • "Copy Prompt" on failures — copy a ready-made prompt to investigate a failure with an AI assistant.

Local report server​

When a run uses streaming mode, the report is written to a .testrelic-report directory rather than a single file, so you view it through the bundled server:

Terminal
testrelic-playwright serve ./test-results/.testrelic-report --port 9323 --open
CommandPurpose
serve ./test-results/.testrelic-report --port 9323 [--host 127.0.0.1] [--open]Start a local server for a streamed report directory
open ./test-results/.testrelic-report [--port 9323]Open a report directory in the browser
tip

Embedded single-file reports don't need the server — just open analytics-timeline.html directly.

Terminal summary​

At the end of a run the plugin prints a summary box to the terminal and, outside of CI, auto-opens the HTML report. Suppress both with quiet = true (or --testrelic-quiet).

Cloud Session Workspace​

When TESTRELIC_API_KEY is set, runs upload to the TestRelic cloud. There, each run opens in the Session Workspace — the same timeline, API calls, assertions, console logs, and artifacts as the local report, backed by the cloud's history and navigation.

Drill into a single test with Run / Test Detail, where you can inspect that test's steps, network activity, and artifacts in context.

Next steps​