> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Playwright Error Grouping in TestDino

> Group failures by root cause with AI-powered classification.

<Callout icon="book-open" color="#3B82F6">
  **What you'll learn**

  * How errors are grouped at run and cross-run levels
  * How AI categorizes failures by root cause
  * How to triage grouped errors to fix multiple tests at once
</Callout>

TestDino groups errors by message and uses AI to categorize failures by root cause. Instead of investigating each failure individually, identify the common cause and fix it.

## Quick Reference

TestDino groups errors at two levels. Use this table to understand how grouping works and locate each view.

| Grouping Level                           | What It Shows                              |
| :--------------------------------------- | :----------------------------------------- |
| [Error message](#view-error-groups)      | Tests that failed with the same error text |
| [Error category](#view-error-categories) | Tests grouped by error type                |

## How Error Grouping Works

When multiple tests fail with similar errors, TestDino groups failures by error message.

TestDino matches errors by:

* Error message text
* Stack trace patterns
* Failure location in code

Similar errors appear as a single group with a count of affected tests.

## View Error Groups

1. Open a test run
2. Go to the **Errors** tab
3. Expand an error group to see all affected tests

<img src="https://testdinostr.blob.core.windows.net/docs/docs/test-runs/error/error-all.webp" alt="Error grouping view showing errors grouped by message with affected test counts" />

## View Error Categories

<Steps>
  <Step title="Go to Analytics">
    Navigate to the Analytics section
  </Step>

  <Step title="Open the Errors tab">
    Click on the Errors tab to view error patterns
  </Step>

  <Step title="View error patterns">
    View error patterns across multiple runs
  </Step>
</Steps>

<img src="https://testdinostr.blob.core.windows.net/docs/docs/analytics/error/error-tiles.webp" alt="Analytics errors view showing error patterns across runs" />

<Note>
  **Note**
  Analytics shows error trends over time. A new error group appearing after a deployment indicates a regression.
</Note>

TestDino classifies errors into categories:

| Category           | Description                                    |
| :----------------- | :--------------------------------------------- |
| Assertion Failures | Expected values did not match actual values    |
| Timeout Issues     | Actions or waits exceeded time limits          |
| Element Not Found  | Locators did not resolve to elements           |
| Network Issues     | HTTP requests failed or returned errors        |
| JavaScript Errors  | Runtime errors in browser or test code         |
| Browser Issues     | Browser launch, context, or rendering problems |
| Other Failures     | Errors outside the above categories            |

Filter by category to focus on specific error types.

## Error Analytics

Open **Analytics → Errors** for trends over time:

[**Error Message Over Time**](/platform/analytics/errors#error-message-over-time)**:** Line graph showing error frequency by category. Identify spikes and trends.

<img src="https://testdinostr.blob.core.windows.net/docs/docs/analytics/error/error-message-over-time.webp" alt="Error trends chart showing error frequency over time by category" />

[**Error Categories Table**](/platform/analytics/errors#error-categories)**:** Breakdown of errors by type with occurrence counts, affected tests, and first/last detected dates.

<img src="https://testdinostr.blob.core.windows.net/docs/docs/analytics/error/error-message.webp" alt="Error categories table showing breakdown by type with occurrence counts" />

Click any error to see all affected test cases.

## Common Error Patterns

<AccordionGroup>
  <Accordion title="Element Not Found">
    `Error: locator.click: Error: strict mode violation`

    Multiple tests targeting the same element fail when the selector breaks. Fix the selector once.
  </Accordion>

  <Accordion title="Timeout">
    `Error: Timeout 30000ms exceeded`

    Often indicates a shared dependency: slow API, missing service, or environment issue. Check what the affected tests have in common.
  </Accordion>

  <Accordion title="Assertion Failure">
    `Error: expect(received).toBe(expected)`

    Same assertion failing across tests may indicate a data issue or application bug affecting multiple pages.
  </Accordion>

  <Accordion title="Network Error">
    `Error: net::ERR_CONNECTION_REFUSED`

    Service unavailable. All tests depending on that service fail together.
  </Accordion>
</AccordionGroup>

## Create Tickets from Error Groups

When an error group needs attention:

<Steps>
  <Step title="Open the error group">
    Navigate to the error group you want to address
  </Step>

  <Step title="Raise an issue">
    Click **Raise Bug** or **Raise Issue**
  </Step>

  <Step title="Select your tool">
    Select Jira, Linear, Asana, or monday
  </Step>

  <Step title="Review and submit">
    TestDino pre-fills the ticket with error details and the affected test count
  </Step>
</Steps>

<Tip>
  **Tip**

  The ticket links back to the error group for context.
</Tip>

## Related

Trace viewer, visual evidence, and debug overview.

<CardGroup cols={2}>
  <Card title="Trace Viewer" icon="timeline" href="/guides/playwright-trace-viewer">
    Step-by-step execution analysis
  </Card>

  <Card title="Visual Evidence" icon="image" href="/guides/debug-playwright-failures/visual-evidence">
    Visual evidence
  </Card>

  <Card title="Error Analytics" icon="chart-line" href="/platform/analytics/errors">
    Error trends over time
  </Card>
</CardGroup>