Skip to main content
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.

​
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
Error grouping view showing errors grouped by message with affected test counts

​
View Error Categories

1

Go to Analytics

Navigate to the Analytics section
2

Open the Errors tab

Click on the Errors tab to view error patterns
3

View error patterns

View error patterns across multiple runs
Analytics errors view showing error patterns across runs
Note Analytics shows error trends over time. A new error group appearing after a deployment indicates a regression.
TestDino classifies errors into categories: Filter by category to focus on specific error types.

​
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

When an error group needs attention:
1

Open the error group

Navigate to the error group you want to address
2

Raise an issue

Click Raise Bug or Raise Issue
3

Select your tool

Select Jira, Linear, Asana, or monday
4

Review and submit

TestDino pre-fills the ticket with error details and the affected test count
TipThe ticket links back to the error group for context.

Trace Viewer

Step-by-step execution analysis

Visual Evidence

Visual evidence

Analytics

Group failures by error signature across runs