Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Cancelling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
      • Spec Files Explorer
      • Error Explorer
      • Reference
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Error Explorer Chart
  • Error Explorer Metrics
  • Occurrences
  • Affected Tests
  • Affected Branches
  • Customization
  • Individual Error Details
  • Customization

Was this helpful?

  1. Dashboard
  2. Test Suite Explorer

Error Explorer

Error Explorer helps to identify the most common errors that are affecting your testing suite.

PreviousSpec Files ExplorerNextReference

Last updated 7 days ago

Was this helpful?

Error Explorer highlights the errors impacting your CI executions, making it easier to identify patterns and root causes.

Currents calculates the metrics by aggregating the results based on the date range and the filters. You can fine-tune the aggregations by applying various filters, for example:

  • What is the most frequent error during the 30-day period affecting main branch?

  • What is the errors affecting most tests tagged onboarding ?

Error Explorer Chart

The Errors Explorer displays a timeline chart showing the daily distribution of error messages over the selected period. You can switch the metric and adjust how many top errors to display. Top errors are ranked by their total value for the selected metric across the period.

Error Explorer Metrics

Occurrences

Shows how often an error has caused a failure or a flaky behavior during the selected period, based on the active filters. This metric counts all occurrences — including repeated ones from the same test.

For example, if the error message TimeoutError: Navigation timeout of 30000 ms exceeded occurred 5 times in test A and 10 more times across other tests, the total count will be 15.

Affected Tests

Shows how many unique tests were impacted by this error during the selected period. Each test is counted once, even if the error occurred multiple times in it.

For example, if the same error appears 5 times in one test and 3 times in another, the Affected Tests count will be 2.

Affected Branches

Shows how many unique branches encountered this error during the selected period. Each branch is counted once, even if the error occurred multiple times on it.

For example, if the error shows up 10 times on main and 3 times on feature/login, the Affected Branches count will be 2.

Customization

Use filters to fine-tune which test recordings are included in the Error Explorer metrics.

  • Date Range - include items recorded within the specified period

  • Tag - include items with the matchingPlaywright Tags

  • Author - include items with the matching Git Author (seeCommit Information)

  • Branch - include items with the matching Git Branch (seeCommit Information)

  • Group - include items recorded for particular group (e.g. Firefox or Chromium)

  • Search by error message - narrow down the results by Error Message

Individual Error Details

Clicking an error item reveals more details about that specific error.

  • Affected Tests – A list of tests impacted by the error, sorted by occurrence. These are tests that failed or flaked due to the error. Click a test title to view its details in the Test Explorer.

  • Recent Executions – A chronologically sorted list of the most recent test runs affected by this error. Clicking on a test title reveal its details in the Test Explorer, clicking on the commit message opens the specific execution details.

  • Affected Branches – A list of branches where this error occurred, sorted by occurrence count.

Customization

Use filters to fine-tune the data that used to calculate the metrics for the Error View:

  • Date Range - include items recorded within the specified period

  • Tag - include items with the matchingPlaywright Tags

  • Author - include items with the matching Git Author (seeCommit Information)

  • Branch - include items with the matching Git Branch (seeCommit Information)

  • Group - include items recorded for particular group (e.g. Firefox or Chromium)

  • Search by error message - narrow down the results by Error Message

Additionally, use the Timeline Chart to focus in the time period of your interest:

Daily Error Distribution - Timeline Chart
Expanding Error Details in Error Explorer
Using Timeline Chart controls to refine Error Explorer view