Skip to main content
The Errors tab groups a run’s failed and flaky tests by error message, then organizes those groups under error categories. Use it to see which errors affected the run, which category they fall into, and how many tests each one impacts.
QA Engineers: spot whether a single error causes most failures or if problems are unrelated. Developers: jump straight to error messages and stack traces without clicking through individual tests.

​
Layout

The tab has a search bar, a Category filter, a Tag filter, and an Expand / Collapse All control across the top. Below them, a summary bar counts the error groups, followed by the error groups themselves grouped under categories. Errors tab with search, Category filter, summary bar, and error groups organized under categories like Assertion Failures and Timeout Issues The summary bar reads “N error groups affecting M tests” and shows failed and flaky totals as colored dots. Categories are collapsible; each header shows how many groups and tests it holds. Search by test name, full title path, error text, or tag. Results update as you type, and matching groups expand automatically so you can read them without clicking.

​
Category filter

Filter the list to one or more error categories. Open the Category dropdown, select the categories you want, and the list narrows to matching groups. Each category in the dropdown shows its group count. Selected categories appear as removable chips with a Clear all option.

​
Tag filter

Filter error groups by test-case tags. Open the Tags dropdown, search or pick one or more tags, and the list shows only groups containing tests with those tags. Tag badges on a group card are also clickable, so selecting a tag from a card toggles the same filter (for example @smoke or @checkout).

​
Expand / Collapse All

The control on the right toggles between Expand All and Collapse All, opening or closing every category and error group at once.

​
Error Groups

Each card is one unique error, grouped by its message signature. The card header shows:
  • The error signature text
  • Failed and flaky counts as colored dots
  • Up to 2 tag badges from the affected tests
Expand a card to list the tests that hit that error in the run.

​
Test Case Rows

Each test row inside a group shows, in order:
  • Status icon: X for failed, a triangle for flaky
  • Test name: the full test case title
  • Duration: how long the test took, next to a timer icon
  • Browser: the browser or device as an icon (Chromium, Firefox, WebKit, Safari, Edge, Android, iOS, and more)
  • Retries: the retry count, shown only when a test retried
Click any test row to open the side panel.
A run over 5,000 tests shows a banner: counts and error groups reflect only the first 5,000 tests. Individual groups that list more tests than shown carry a “showing first N of M” note.

​
Side Panel

The side panel opens from the right and shows one test case without leaving the Errors tab. Side panel showing test case title, file path, inline metadata, error message, stack trace, and View Full Details button The test name, its status as a colored icon, the spec file path, and an inline metadata line: duration, browser, retry count, and how long ago the test ran.

​
Error Message

The Playwright error text for the failing attempt, with ANSI color codes stripped for readability.

​
Stack Trace

The call stack at the point of failure, shown when the test recorded one. Use it to trace back to the exact line in your test or application code.

​
View Full Details

Opens the full test case details page. From there you reach the Overview, History, and Insights tabs for deeper analysis.

Summary

Group failures by cause

Specs

Review results by spec file

Flaky Test Detection

Why tests pass on retry and how to fix them

Analytics

Track reliability and duration trends over runs