UI CoveragePremium Solution
Changelog
Week of 12/19/2025​
- The
elementFilters,elements,elementGroups, andallowedInteractionCommandsconfiguration properties now support an optionaldocumentScopefield that allows you to scope selectors to specific document hosts (iframes or shadow DOM hosts). This enables you to target elements within nested document contexts without requiring DOM changes. For example, you can filter, identify, group, or restrict interactions for elements within a specific shadow DOM component or iframe by combining a selector withdocumentScope. Multiple document hosts can be chained in the array to target elements within nested documents (e.g., an iframe containing a shadow DOM component). See the Element Filters, Elements, Element Groups, and Allowed Interaction Commands documentation for more details and examples.
Week of 12/12/2025​
- The
profilesconfiguration property allows you to use different configuration settings for different runs based on run tags. This enables you to customize UI Coverage behavior for different environments, branches, or test scenarios. See the Profiles guide for more details. - All configuration objects now support an optional
commentproperty that you can use to provide context and explanations for why certain values are set. This helps make your configuration easier to understand and maintain, especially when working in teams or revisiting configuration after some time. - A new guide on blocking pull requests and setting policies is now available. This guide demonstrates how to use the Results API to enforce test coverage standards, compare results against baselines, and automatically block pull requests when coverage thresholds are not met.
Week of 6/23/25​
UI Coverage now supports defining custom commands that will count towards coverage scores, restricting which kinds of interactions are allowed for certain elements, and including assertions in the UI Coverage calculations. See the following new properties for more details:
Week of 6/2/2025​
- We now support fetching UI Coverage results from Drone CI with the Results API.
Week of 5/26/2025​
- Launched AI-powered Test Generation in Cypress Cloud, to help you quickly add tests for the untested elements detected in UI Coverage reports, in a way that follows your existing practices and conventions. For more details, read our blog post.
Week of 5/12/2025​
- We now support fetching UI Coverage results from AWS CodeBuild with the Results API.
Week of 4/1/2024​
- Shadow DOM and iFrame Support: UI Coverage now supports Shadow DOM and iFrames for reporting on interactions. Both of these settings are off by default. Please contact your Cypress representative to opt in.
Week of 3/24/2025​
- UI Coverage results are now included in the Data Extract API so that you can retrieve data over time.
Week of 1/15/2024​
- Branch Review Integration (Beta): Added UI Coverage comparisons to Branch Review, enabling teams to see how code changes impact test coverage across branches. Available for all Git providers and includes manual run selection for customized comparisons.
Week of 12/16/2023​
- URL Handling: Fixed issues with URLs containing special characters (like parentheses) that could break view generation.
- Performance Improvements: Optimized rendering performance for reports containing large numbers of elements and snapshots.
Week of 10/7/2024​
- Improved Table Grouping: The default grouping rules have been updated to more accurately identify and group elements in tables.
Week of 9/30/2024​
- Slack Messages: UI Coverage results results are now included in Slack messages alongside test results. Learn more about our Slack integration here.
Week of 9/23/2024​
- Improved Link Display Logic: Links will now more consistently display across the reports, matching defined views more closely.
Week of 9/9/2024​
- Element Tooltips: We have improved the user experience of UI Coverage by adding tooltips for elements, emphasizing their selectors, making it easier to navigate coverage reports and identify elements.
Week of 8/19/2024​
- Results API: We have added the new Results API which enables you to programmatically fetch your run's UI Coverage results in a CI environment. This allows you to act the results within CI by allowing you to determine if the results are acceptable or need to be addressed before code changes can merge.
- Pull and Merge Request Comments: UI Coverage results will now appear in GitHub, GitLab and Bitbucket pull request and merge request comments alongside test results. Integrations can be installed and comments can be enabled in Project Settings.
Week of 8/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 value of the class attribute.
Week of 8/5/2024​
- View Untested Elements: You can now quickly access all of the 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 UI Coverage configuration to ignore certain elements.
- View Tested Elements: You can now quickly access all of the tested elements across all views in the "Tested elements" section. Identify potential redundant coverage by looking through the elements with the highest numbers of interactions and tests.
Week of 7/22/2024​
- View Untested Links: You can now quickly access all of the 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 UI Coverage configuration to ignore certain links.
Week of 6/24/2024​
- View configuration information for each run in the properties tab: There, you'll find the configuration set for the project at the start of the run. This will help you understand what factors might be driving a score change. This helps distinguish config criteria changes from other factors such as changes to your application, tests, Cypress versions, and more.
- Anchor elements considered interactive: Anchor elements (
atags) are now considered interactive even when they do not have anhrefattribute.
Week of 5/20/2024​
- Manage Configuration in Project Settings: Added the ability to configure what should be tested or ignored in your score calculations to ensure your team is capturing what's relevant to your testing strategy. This feature allows owners and admins to easily update and manage settings using an editor within Project Settings.
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 3/25/2024​
- Project-Level Configuration Options: UI Coverage now supports project-level configuration, enabling users to customize UI Coverage settings without updating their HTML. Users can exclude specific URLs and elements by selector and group elements to simplify coverage analysis. For configuration assistance, contact your Account Executive.
Week of 3/4/2024​
- Element Interaction Details: UI Coverage now provides detailed insights into the testing status of every interactive element, including interaction types, frequency, and locations within the UI. A new tracking system shows where each element has been identified and tested, and link details indicate visit frequency.
Week of 2/26/2024​
- Element Grouping Improvements: Introduced "cascade" behavior for the
data-cy-ui-groupattribute, which now allows users to place the attribute on a wrapper or parent element, so that it pass grouping values to child interactive elements. - Text Filter: Text filtering has been added to UI Coverage reports, allowing users to filter the "Views" list by name for easy searching.
Week of 12/31/2023​
- URL Grouping: UI Coverage reports now intelligently group repeated URLs to reduce duplicate Views. This update simplifies reports, making it easier to identify and prioritize issues by minimizing duplicate Views, resulting in a more polished and user-friendly experience.