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
        • Tests Performance
      • Spec Files Explorer
        • Spec Files Performance
      • Errors Explorer
  • 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
  • Spec Explorer Metrics
  • Duration
  • Failure Rate
  • Timeout Rate
  • Flakiness Rate
  • Suite Size
  • Executions
  • Filters
  • Controls & Settings
  • Use Cases

Was this helpful?

  1. Dashboard
  2. Test Suite Explorer

Spec Files Explorer

Spec-level health and performance dashboard - flakiness, failure rate, duration, suite size

PreviousTests PerformanceNextSpec Files Performance

Last updated 25 days ago

Was this helpful?

The Spec Files Explorer allows users to track and analyze spec files performance using various metrics like:

  • Duration

  • Failure Rate

  • Flakiness Rate

  • Timeout Rate

  • Suite Size

Currents calculates the metrics based on the executions recorded during the provided date range and filters. A typical use case is to monitor the performance of the spec files that cause the degraded performance of the overall test suite - e.g. spec files with the highest flakiness rate, longest duration etc.

Spec Explorer Metrics

Duration

The average duration of , excluding timed-out or cancelled spec files. You can exclude or include failed executions for calculating the average duration in Settings (see below).

Failure Rate

The failure rate is the percentage of spec file executions that failed. A spec file is failed if it had 1 or more failed tests. See Spec File Status.

Timeout Rate

The percentage of spec file executions that timed out. A spec file is marked as timed out if we didn't report its test results before exceeding its run's timeout. See Run Timeouts.

Flakiness Rate

The percentage of spec file executions that had 1 or more flaky tests. See Flaky Tests.

Suite Size

The number of tests in a spec file (including skipped tests).

Only fully completed executions of a spec file are considered for counting the suite size

Executions

How many executions were included during in the selected period and match the filters.

Filters

Only test recordings matching the filters will be included for metric calculation.

  • Date Range - include items recorded within the specified period

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

  • Search by spec name - narrow down the results by spec name

Controls & Settings

  • Click on a column header to sort the tests by the corresponding column, click again to change the sorting order.

    • Include Failed Executions - include or exclude the failed execution in calculating the avg. duration

Use Cases

  • The flakiest Spec Files from the selected period for a specific branch.

  • The Failure Rate trends for specific branches for the past month.

  • The most long-running Spec Files and how they changed their duration over time.

  • The Spec Files that experienced the most timeouts in the past weeks.

Clicking on an individual spec file will reveal a detailed drill-down of the selected spec file performance, including a detailed history of execution, top errors, etc. See Spec Files Performance.

Explore individual spec details by clicking on its name and opening Spec Files Performance view; and also schedule containing the highlights of the Spec Files health and performance metrics delivered to your inbox.

Tag - include items with the matching

Author - include items with the matching Git Author (see )

Branch - include items with the matching Git Branch (see )

Click on the Export icon to download the data in JSON format

Click in the Settings icon to customize the view:

Automated Reports
Playwright Tags
Commit Information
Commit Information
Spec Files Explorer health and performance dashboard - flakiness, failure rate, duration, suite size.
Spec Explorer Settings
Spec Files Explorer