Skip to main content
TestDino groups failures that share a cause, and uses AI to categorize them by root cause. Instead of investigating each failure individually, identify the common cause and fix it.

​
Quick Reference

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

​
How Error Grouping Works

When multiple tests fail on the same thing, TestDino groups them into 1 error group. TestDino matches errors by:
  • The element or request that failed, with the expected value and the reason
  • The screenshot name on a visual failure
  • The step a test timeout interrupted
Quoted expected values in the message are kept. IDs, URLs, timestamps, timeouts, and similar run-specific values are dropped, and the stack trace plays no part, so the same failure on the same element stays in 1 group across runs. Failures that name different elements stay in separate groups, so a broken selector that appears in several places shows as several groups. 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
The full tab layout is described on the Errors tab page.

​
View Error Categories

On a test run’s Errors tab, error groups are organized under categories. TestDino classifies errors into these categories: Use the Category filter on the Errors tab to focus on 1 or more categories.

​
Error clusters across runs

Add the Error clusters widget to an analytics dashboard to group repeated failures by error signature across runs. Each cluster shows the shared error and the tests it affects, so you can find and prioritize the failures that hit the most tests. Click any error to see all affected test cases.

​
Common Error Patterns

Error: locator.click: Error: strict mode violationMultiple tests targeting the same element fail when the selector breaks. Fix the selector once.
Error: Timeout 30000ms exceededOften indicates a shared dependency: slow API, missing service, or environment issue. Check what the affected tests have in common.
Error: expect(received).toBe(expected)Same assertion failing across tests may indicate a data issue or application bug affecting multiple pages.
Error: net::ERR_CONNECTION_REFUSEDService unavailable. All tests depending on that service fail together.

​
Create Tickets from Error Groups

Error groups have no ticket control of their own. To file a ticket for an error group:
  1. On the Errors tab, expand the group and click a test case in it.
  2. In the side panel, click View Full Details.
  3. On the test case page, click Raise Issue and select a connected tool.
Connecting a tool is covered in the Jira, Linear, Asana, and monday guides.

Trace Viewer

Step-by-step execution analysis

Visual Evidence

Visual evidence

Analytics

Group failures by error signature across runs
Last modified on October 13, 2026