--- id: ui-coverage/faq title: UI Coverage FAQ description: >- Get answers to common questions about Cypress UI Coverage, including scores, view and URL grouping, element grouping and filtering, iframes and shadow DOM, and configuration. section: ui-coverage source_path: docs/ui-coverage/faq.mdx version: 3b85801b725bd02bf0cb58cedaf42944712cdc72 updated_at: '2026-07-12T03:11:07.806Z' --- # UI Coverage FAQ ## General ### What is UI Coverage? [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) is a Cypress Cloud feature that shows you which interactive elements of your application your tests actually exercise. Every recorded run produces a visual report of tested and untested elements across all of your application's [views](/llm/markdown/ui-coverage/core-concepts/views.md), along with a coverage score you can track over time. ### Do I need to install anything to use UI Coverage? No. UI Coverage requires no code changes or instrumentation. Reports are generated from [Test Replay](/llm/markdown/cloud/features/test-replay.md) data, so any run recorded to Cypress Cloud with Test Replay on Cypress v13 or later is ready to use. See [setup](/llm/markdown/ui-coverage/get-started/setup.md) for details. ### How is the UI Coverage score calculated? The score compares the number of tested interactive elements to the total number of interactive elements in your application. [Grouped elements](/llm/markdown/ui-coverage/core-concepts/element-grouping.md) count as a single unit: the group counts once toward the total, and an interaction with any element in the group marks the whole group as tested. ## Views and URLs ### Why do similar URLs show up as separate views? Automatic grouping only replaces path segments that are numbers or IDs (UUIDs and UUID-like values) with a wildcard. Segments like usernames or slugs are not recognized as dynamic, so `/users/alice` and `/users/bob` remain separate views. Add a [`views`](/llm/markdown/ui-coverage/configuration/views.md) pattern to group them yourself. See [how views are created](/llm/markdown/ui-coverage/core-concepts/views.md#How-views-are-created) for the full set of automatic rules. ### Do query parameters create separate views? No. Query strings are ignored when grouping, so `/dashboard?tab=overview` and `/dashboard?tab=settings` become a single `/dashboard` view. If a query parameter meaningfully changes the page, use a [`views`](/llm/markdown/ui-coverage/configuration/views.md) pattern with `groupBy` on that parameter to split it into separate views. ### How do I exclude URLs from UI Coverage? Add a [`viewFilters`](/llm/markdown/ui-coverage/configuration/viewfilters.md) rule with `include: false` for a URL pattern. Excluding a URL removes its snapshots from the report and stops links pointing to it from counting against your coverage score. The [Ignore views and links](/llm/markdown/ui-coverage/guides/ignore-views-and-links.md) guide walks through common cases. ### Why is a page missing from my report? Views are created from URLs your tests actually visit, so a page that no test navigates to has no view. Check [untested links](/llm/markdown/ui-coverage/core-concepts/interactivity.md#Untested-Links) in the report — pages that are linked to but never visited appear there. Also confirm that a [`viewFilters`](/llm/markdown/ui-coverage/configuration/viewfilters.md) rule isn't excluding the page unintentionally. ## Element grouping and identification ### What happens if two elementGroups rules match the same element? The first matching rule in your [`elementGroups`](/llm/markdown/ui-coverage/configuration/elementgroups.md) configuration wins, so list specific rules before broad catch-all rules. A rule that appears after another rule matching the same elements never applies to them. ### Can I group or filter elements inside iframes or shadow DOM? Yes. The [`elementGroups`](/llm/markdown/ui-coverage/configuration/elementgroups.md), [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), and [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) configuration options all accept a `documentScope` property that limits a rule to elements inside specific iframes or shadow DOM hosts. List one CSS selector per host, ordered from the outermost document to the innermost. ### Why isn't my element group showing up in the report? The most common causes are: * An earlier `elementGroups` rule matches the same elements, and the first matching rule wins. * The elements are excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), so they're never considered for grouping. * The elements declare a group in markup with the `data-cy-ui-group` attribute, which takes priority over configuration rules. * The selector matches a container rather than the interactive elements themselves. * The report was processed before you saved the configuration. Regenerate the run to apply the current configuration. ### How do I exclude elements from UI Coverage? Add an [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md) rule with `include: false` for a CSS selector that matches the elements. Excluded elements are removed from the report and don't count toward your coverage score. This is the standard way to remove third-party widgets, such as chat launchers or cookie banners, from your reports. The [Ignore elements](/llm/markdown/ui-coverage/guides/ignore-elements.md) guide walks through common cases. ### Do excluded elements count toward my UI Coverage score? No. An element excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md) doesn't appear in the report and doesn't count toward the score, whether your tests interacted with it or not. It's also not considered by [`elementGroups`](/llm/markdown/ui-coverage/configuration/elementgroups.md) or [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) rules. ### Why isn't my elementFilters rule excluding an element? The most common causes are: * The selector matches a container instead of the element itself. Filters use standard CSS matching against each tracked element, so `footer` matches only the `