Run & Test Case Detail
TestRelic provides two levels of detail for every test execution: the Run Detail view (one invocation of your suite) and the Test Case Detail view (one individual test).
Run Detail page
The Run Detail page (/dashboards/test-runs/:runId) shows the full context of a single test run:
- Run metadata — Repository, branch, environment, CI system, total duration, timestamp.
- Test case table — All tests in the run with their pass/fail/flaky status and individual durations.
- Status filter tabs — Quickly switch between All, Passed, Failed, and Flaky views.
- Navigation — Click any row to open the Test Case Detail view for that session.
CI context
If the run was triggered from a CI pipeline, the Run Detail page shows the CI system context:
- Build ID or run number
- Commit SHA and branch
- CI system (GitHub Actions, GitLab CI, Jenkins, CircleCI)
- Link to the CI job when the GitHub Actions integration is connected
Test Case Detail page
The Test Case Detail page (/dashboards/test-runs/:runId/cases/:caseId) is a resizable, multi-panel workspace for inspecting a single test case. It is the primary debugging interface in TestRelic.
The layout is split into a main content area on the left and a DevTools-style panel on the right, with a resizable divider.
Main panels
- Overview
- Steps
- Console
- Network
The Overview panel shows the test case summary:
- Test name, file path, and tags
- Final status (passed, failed, skipped, flaky)
- Total duration and number of retries
- Error message and source code location (for failures)
- Stack trace (when available)
The Steps panel renders the full step-by-step execution timeline, extracted from Playwright's trace. Each step shows:
- Step name and action type
- Duration
- Screenshot thumbnail (when available)
- Associated network requests for that step
Console output captured during the test run, including:
console.log,console.warn, andconsole.errormessages- Browser-generated errors
- Error classification and normalization (using the built-in log normalizer)
All HTTP requests made during the test session:
- Request method, URL, status code, and duration
- Failed requests highlighted in red
- Response size and resource type (XHR, script, image, etc.)
- Filterable by status or resource type
Additional panels
| Panel | Description |
|---|---|
| Performance | Timing metrics for the test session including navigation timing and resource load breakdown |
| Detected Issues | Automatically classified issues found in the session (e.g. console errors, failed requests, accessibility violations) |
| Jira | Link or create Jira issues directly from a test case. Requires the Jira integration |
| GitHub Actions | CI build timeline and workflow trigger for the run that produced this session. Requires the GitHub Actions integration |
| Analytics Events | Amplitude analytics events captured during the session. Requires the Amplitude integration |
Video recording
If the test session includes a video recording (Playwright's video option enabled), it is displayed in the workspace alongside the step timeline. The video player:
- Synchronizes playback with the step timeline — clicking a step seeks the video to that moment.
- Adapts to mobile device frame dimensions when the test ran in a mobile viewport.
- Shows screenshots as a fallback when video is not available.
Jira quick-create
In the Test Case Detail view, the Jira panel provides a Quick Create sheet that pre-fills a Jira issue with:
- The test name as the issue summary
- The error message and stack trace in the description
- A direct link back to the test case session in the issue body
This saves significant time when triaging failures and converting them into tracked work items.
Every test case detail view has a unique, shareable URL. Copy the URL from the browser to share a specific session with a teammate for review or investigation.