Skip to main content
UI CoveragePremium Solution

Changelog

Week of May 18, 2026​

  • UI Coverage in Enterprise Reporting: UI Coverage trends are now available in the Enterprise Reporting area of Cypress Cloud, so you can track coverage scores across all projects and runs and see when they improve or drift over time. See the Monitor Changes guide for details.

Week of Apr 27, 2026​

  • UI Coverage in Cypress Cloud MCP: AI agents can now query UI Coverage for a run through the Cypress Cloud MCP server, using three new tools:

    • cypress_get_ui_coverage_report: Returns a run's overall coverage score, tested and untested element and link counts, and the riskiest views.
    • cypress_get_ui_coverage_views: Browses all of the views in a run beyond the riskiest ones in the report.
    • cypress_get_ui_coverage_elements: Drills down into individual elements, with filtering by tested or untested status and by view.

    The cypress_get_runs tool now also reports each run's UI Coverage score. See working with AI agents for example prompts and setup.

Week of Feb 06, 2026​

  • Buildkite support for the Results API: You can now fetch UI Coverage results from Buildkite CI using the Results API.

Week of Jan 16, 2026​

  • Bitbucket support for the Results API: You can now fetch UI Coverage results from Bitbucket CI using the Results API.

Week of Dec 19, 2025​

  • Document scoping for nested contexts (documentScope): The elementFilters, elements, elementGroups, and allowedInteractionCommands configuration properties now accept an optional documentScope field that scopes selectors to specific document hosts, such as iframes or shadow DOM hosts. This lets you filter, identify, group, or restrict interactions for elements inside nested document contexts without changing your application's DOM. Chain multiple hosts in the array to target elements within nested documents, such as an iframe that contains a shadow DOM component. See the Element Filters, Elements, Element Groups, and Allowed Interaction Commands documentation for details and examples.

Week of Dec 12, 2025​

  • Per-run configuration with profiles: The profiles configuration property lets you apply different configuration settings to different runs based on run tags. Use it to customize UI Coverage behavior for specific environments, branches, or test scenarios. See the Profiles guide for details.
  • Inline configuration comments: All configuration objects now support an optional comment property for documenting why a value is set. Comments make your configuration easier to understand and maintain, especially across teams or when revisiting it later.
  • Guide: block pull requests and set policies: A new guide on blocking pull requests and setting policies shows how to use the Results API to enforce coverage standards, compare results against baselines, and automatically block pull requests when coverage thresholds are not met.

Week of Jun 23, 2025​

  • Custom interaction commands: UI Coverage now lets you define custom commands that count toward coverage scores, restrict which kinds of interactions are allowed for certain elements, and include assertions in coverage calculations. See the new configuration properties:

Week of Jun 02, 2025​

  • Drone CI support for the Results API: You can now fetch UI Coverage results from Drone CI using the Results API.

Week of May 26, 2025​

  • AI-powered Test Generation: We launched Test Generation in Cypress Cloud to help you quickly add tests for the untested elements found in UI Coverage reports, following your existing practices and conventions. Read about adding your missing tests faster with Test Generation for details.

Week of May 12, 2025​

  • AWS CodeBuild support for the Results API: You can now fetch UI Coverage results from AWS CodeBuild using the Results API.

Week of Apr 14, 2025​

  • Shadow DOM and iframe support: UI Coverage can now report on interactions inside Shadow DOM and iframes. Both are off by default. Contact your Cypress representative to opt in.

Week of Mar 24, 2025​

  • UI Coverage in the Data Extract API: UI Coverage results are now available through the Data Extract API, so you can retrieve and analyze your coverage data over time.

Week of Jan 15, 2025​

  • Branch Review integration (Beta): UI Coverage comparisons are now available in Branch Review, so teams can see how code changes affect test coverage across branches. Comparisons work for all Git providers and support manual run selection for customized comparisons.

Week of Dec 16, 2024​

  • URL handling: Fixed issues with URLs containing special characters, such as parentheses, that could break view generation.
  • Performance improvements: Optimized rendering performance for reports that contain large numbers of elements and snapshots.

Week of Oct 07, 2024​

  • Improved table grouping: The default grouping rules now identify and group elements in tables more accurately.

Week of Sep 30, 2024​

  • Slack messages: UI Coverage results now appear in Slack messages alongside test results. See our Slack integration for setup details.

Week of Sep 23, 2024​

  • Improved link display logic: Links now display more consistently across reports, matching your defined views more closely.

Week of Sep 09, 2024​

  • Element tooltips: UI Coverage now shows tooltips for elements that emphasize their selectors, making it easier to navigate coverage reports and identify elements.

Week of Aug 19, 2024​

  • Results API: The new Results API lets you programmatically fetch a run's UI Coverage results in a CI environment. You can act on the results within CI to determine whether they are acceptable or need to be addressed before code changes can merge.
  • Pull and merge request comments: UI Coverage results now appear in GitHub, GitLab, and Bitbucket pull request and merge request comments alongside test results. Install integrations and enable comments in Project Settings.

Week of Aug 12, 2024​

  • Improved attributeFilters behavior: When matching against class attributes, the attributeFilters configuration option now targets and filters individual class names rather than the entire class attribute value.

Week of Aug 05, 2024​

  • View untested elements: You can now quickly access all untested elements across all views in the "Untested elements" section. Save time and improve your coverage by testing these areas of your application, or use elementFilters in your UI Coverage configuration to ignore certain elements.
  • View tested elements: You can now quickly access all tested elements across all views in the "Tested elements" section. Spot potentially redundant coverage by reviewing the elements with the highest numbers of interactions and tests.

Week of Jul 22, 2024​

  • View untested links: You can now quickly access all untested links across all views in the "Untested links" section. Save time and improve your coverage by testing these areas of your application, or use viewFilters in your UI Coverage configuration to ignore certain links.

Week of Jun 24, 2024​

  • View configuration information for each run: The properties tab now shows the configuration set for the project at the start of the run. This helps you understand what might be driving a score change and distinguishes configuration changes from other factors, such as changes to your application, tests, and Cypress versions. See viewing configuration for a run.
  • Anchor elements considered interactive: Anchor elements (a tags) are now considered interactive even when they do not have an href attribute.

Week of May 20, 2024​

  • Manage configuration in Project Settings: Owners and admins can now configure what should be tested or ignored in score calculations using an editor within Project Settings, so your team captures what's relevant to your testing strategy:
    • elementFilters: Exclude specific elements by CSS selector.
    • views: Define URL patterns for grouping in the UI.
    • viewFilters: Exclude groups of URLs from reports.
    • attributeFilters: Determine which attributes are used for identifying and grouping elements.
    • elementGroups: Create custom rules for grouping elements to reduce noise in scores.
    • significantAttributes: Prioritize custom attributes over defaults for element identification and grouping.

Week of Mar 25, 2024​

  • Project-level configuration options: UI Coverage now supports project-level configuration, so you can customize UI Coverage settings without updating your HTML. Exclude specific URLs and elements by selector, and group elements to simplify coverage analysis. For configuration assistance, contact your Account Executive.

Week of Mar 04, 2024​

  • Element interaction details: UI Coverage now provides detailed insights into the testing status of every interactive element, including interaction types, frequency, and location within the UI. A new tracking system shows where each element has been identified and tested, and link details indicate visit frequency.

Week of Feb 26, 2024​

  • Element grouping improvements: The data-cy-ui-group attribute now supports "cascade" behavior, so you can place it on a wrapper or parent element to pass grouping values down to child interactive elements.
  • Text filter: You can now filter the "Views" list by name, making it easier to search UI Coverage reports.

Week of Dec 31, 2023​

  • URL grouping: UI Coverage reports now intelligently group repeated URLs to reduce duplicate views. This simplifies reports and makes it easier to identify and prioritize issues.

Contents