{
  "doc": {
    "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": "/llm/markdown/ui-coverage/faq.md",
    "version": "3b85801b725bd02bf0cb58cedaf42944712cdc72",
    "updated_at": "2026-07-12T03:11:07.806Z",
    "headings": [
      {
        "id": "ui-coverage/faq#ui-coverage-faq",
        "text": "UI Coverage FAQ",
        "level": 1
      },
      {
        "id": "ui-coverage/faq#general",
        "text": "General",
        "level": 2
      },
      {
        "id": "ui-coverage/faq#what-is-ui-coverage",
        "text": "What is UI Coverage?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#do-i-need-to-install-anything-to-use-ui-coverage",
        "text": "Do I need to install anything to use UI Coverage?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#how-is-the-ui-coverage-score-calculated",
        "text": "How is the UI Coverage score calculated?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#views-and-urls",
        "text": "Views and URLs",
        "level": 2
      },
      {
        "id": "ui-coverage/faq#why-do-similar-urls-show-up-as-separate-views",
        "text": "Why do similar URLs show up as separate views?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#do-query-parameters-create-separate-views",
        "text": "Do query parameters create separate views?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#how-do-i-exclude-urls-from-ui-coverage",
        "text": "How do I exclude URLs from UI Coverage?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#why-is-a-page-missing-from-my-report",
        "text": "Why is a page missing from my report?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#element-grouping-and-identification",
        "text": "Element grouping and identification",
        "level": 2
      },
      {
        "id": "ui-coverage/faq#what-happens-if-two-elementgroups-rules-match-the-same-element",
        "text": "What happens if two elementGroups rules match the same element?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#can-i-group-or-filter-elements-inside-iframes-or-shadow-dom",
        "text": "Can I group or filter elements inside iframes or shadow DOM?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#why-isnt-my-element-group-showing-up-in-the-report",
        "text": "Why isn't my element group showing up in the report?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#how-do-i-exclude-elements-from-ui-coverage",
        "text": "How do I exclude elements from UI Coverage?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#do-excluded-elements-count-toward-my-ui-coverage-score",
        "text": "Do excluded elements count toward my UI Coverage score?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#why-isnt-my-elementfilters-rule-excluding-an-element",
        "text": "Why isn't my elementFilters rule excluding an element?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#can-i-exclude-elements-from-ui-coverage-without-affecting-cypress-accessibility",
        "text": "Can I exclude elements from UI Coverage without affecting Cypress Accessibility?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#why-does-one-element-appear-as-multiple-elements-in-the-report",
        "text": "Why does one element appear as multiple elements in the report?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#why-isnt-my-elements-rule-applying",
        "text": "Why isn't my elements rule applying?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#configuration",
        "text": "Configuration",
        "level": 2
      },
      {
        "id": "ui-coverage/faq#where-do-i-set-ui-coverage-configuration",
        "text": "Where do I set UI Coverage configuration?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#do-i-need-to-rerun-my-tests-after-changing-configuration",
        "text": "Do I need to rerun my tests after changing configuration?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#can-i-use-different-configuration-for-different-runs",
        "text": "Can I use different configuration for different runs?",
        "level": 3
      },
      {
        "id": "ui-coverage/faq#see-also",
        "text": "See also",
        "level": 2
      }
    ]
  },
  "chunks": [
    {
      "id": "ui-coverage/faq#general",
      "doc_id": "ui-coverage/faq",
      "heading": "General",
      "heading_level": 2,
      "content_markdown": "## General\n\n### What is UI Coverage?\n\n[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.\n\n### Do I need to install anything to use UI Coverage?\n\nNo. 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.\n\n### How is the UI Coverage score calculated?\n\nThe 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "general"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 215
    },
    {
      "id": "ui-coverage/faq#what-is-ui-coverage",
      "doc_id": "ui-coverage/faq",
      "heading": "What is UI Coverage?",
      "heading_level": 3,
      "content_markdown": "### What is UI Coverage?\n\n[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.\n",
      "section": "ui-coverage",
      "anchors": [
        "what-is-ui-coverage"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 71
    },
    {
      "id": "ui-coverage/faq#do-i-need-to-install-anything-to-use-ui-coverage",
      "doc_id": "ui-coverage/faq",
      "heading": "Do I need to install anything to use UI Coverage?",
      "heading_level": 3,
      "content_markdown": "### Do I need to install anything to use UI Coverage?\n\nNo. 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "do-i-need-to-install-anything-to-use-ui-coverage"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 67
    },
    {
      "id": "ui-coverage/faq#how-is-the-ui-coverage-score-calculated",
      "doc_id": "ui-coverage/faq",
      "heading": "How is the UI Coverage score calculated?",
      "heading_level": 3,
      "content_markdown": "### How is the UI Coverage score calculated?\n\nThe 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "how-is-the-ui-coverage-score-calculated"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 75
    },
    {
      "id": "ui-coverage/faq#views-and-urls",
      "doc_id": "ui-coverage/faq",
      "heading": "Views and URLs",
      "heading_level": 2,
      "content_markdown": "## Views and URLs\n\n### Why do similar URLs show up as separate views?\n\nAutomatic 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.\n\n### Do query parameters create separate views?\n\nNo. 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.\n\n### How do I exclude URLs from UI Coverage?\n\nAdd 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.\n\n### Why is a page missing from my report?\n\nViews 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "views-and-urls"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 297
    },
    {
      "id": "ui-coverage/faq#why-do-similar-urls-show-up-as-separate-views",
      "doc_id": "ui-coverage/faq",
      "heading": "Why do similar URLs show up as separate views?",
      "heading_level": 3,
      "content_markdown": "### Why do similar URLs show up as separate views?\n\nAutomatic 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-do-similar-urls-show-up-as-separate-views"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 87
    },
    {
      "id": "ui-coverage/faq#do-query-parameters-create-separate-views",
      "doc_id": "ui-coverage/faq",
      "heading": "Do query parameters create separate views?",
      "heading_level": 3,
      "content_markdown": "### Do query parameters create separate views?\n\nNo. 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "do-query-parameters-create-separate-views"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 61
    },
    {
      "id": "ui-coverage/faq#how-do-i-exclude-urls-from-ui-coverage",
      "doc_id": "ui-coverage/faq",
      "heading": "How do I exclude URLs from UI Coverage?",
      "heading_level": 3,
      "content_markdown": "### How do I exclude URLs from UI Coverage?\n\nAdd 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "how-do-i-exclude-urls-from-ui-coverage"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 68
    },
    {
      "id": "ui-coverage/faq#why-is-a-page-missing-from-my-report",
      "doc_id": "ui-coverage/faq",
      "heading": "Why is a page missing from my report?",
      "heading_level": 3,
      "content_markdown": "### Why is a page missing from my report?\n\nViews 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-is-a-page-missing-from-my-report"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 76
    },
    {
      "id": "ui-coverage/faq#element-grouping-and-identification",
      "doc_id": "ui-coverage/faq",
      "heading": "Element grouping and identification",
      "heading_level": 2,
      "content_markdown": "## Element grouping and identification\n\n### What happens if two elementGroups rules match the same element?\n\nThe 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.\n\n### Can I group or filter elements inside iframes or shadow DOM?\n\nYes. 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.\n\n### Why isn't my element group showing up in the report?\n\nThe most common causes are:\n\n*   An earlier `elementGroups` rule matches the same elements, and the first matching rule wins.\n*   The elements are excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), so they're never considered for grouping.\n*   The elements declare a group in markup with the `data-cy-ui-group` attribute, which takes priority over configuration rules.\n*   The selector matches a container rather than the interactive elements themselves.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n\n### How do I exclude elements from UI Coverage?\n\nAdd 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.\n\n### Do excluded elements count toward my UI Coverage score?\n\nNo. 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.\n\n### Why isn't my elementFilters rule excluding an element?\n\nThe most common causes are:\n\n*   The selector matches a container instead of the element itself. Filters use standard CSS matching against each tracked element, so `footer` matches only the `<footer>` element. Use a descendant selector like `footer *` to exclude everything inside a container.\n*   An earlier `elementFilters` rule already matched the element, and the first matching rule wins. An `include: true` rule above your exclude rule protects the elements it matches.\n*   The rule has a `documentScope` that doesn't match the element's iframe or shadow DOM hosts.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n\n### Can I exclude elements from UI Coverage without affecting Cypress Accessibility?\n\nYes. An `elementFilters` list at the root of your configuration applies to both products, but nesting it under a `uiCoverage` or `accessibility` key applies it to that product only. A nested list completely replaces a root-level one for that product; the two are not merged. See [Exclude elements](/llm/markdown/ui-coverage/configuration/elementfilters.md#Scope).\n\n### Why does one element appear as multiple elements in the report?\n\nThis usually means the element's identifying attributes change between [snapshots](/llm/markdown/ui-coverage/core-concepts/element-identification.md#Snapshots), for example auto-generated IDs or dynamic class names. Use [`attributeFilters`](/llm/markdown/ui-coverage/configuration/attributefilters.md) to ignore the dynamic attributes, or [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) to define the element's identity explicitly. See [troubleshooting](/llm/markdown/ui-coverage/troubleshooting.md) for more scenarios.\n\n### Why isn't my elements rule applying?\n\nAn [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) rule applies only when its selector matches exactly one interactive element in a snapshot. The most common causes are:\n\n*   The selector matches more than one interactive element in the same snapshot, so the rule is skipped for that snapshot. Add [`documentScope`](/llm/markdown/ui-coverage/configuration/elements.md#Options) or a more specific selector, or use [`elementGroups`](/llm/markdown/ui-coverage/configuration/elementgroups.md) if several elements should share an identity.\n*   The selector only matches non-interactive elements, such as a wrapper around the actual button or input.\n*   The element is excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), so it's never considered.\n*   A later `elements` rule matches the same element, and the last matching rule wins.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n",
      "section": "ui-coverage",
      "anchors": [
        "element-grouping-and-identification"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 872
    },
    {
      "id": "ui-coverage/faq#what-happens-if-two-elementgroups-rules-match-the-same-element",
      "doc_id": "ui-coverage/faq",
      "heading": "What happens if two elementGroups rules match the same element?",
      "heading_level": 3,
      "content_markdown": "### What happens if two elementGroups rules match the same element?\n\nThe 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "what-happens-if-two-elementgroups-rules-match-the-same-element"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 57
    },
    {
      "id": "ui-coverage/faq#can-i-group-or-filter-elements-inside-iframes-or-shadow-dom",
      "doc_id": "ui-coverage/faq",
      "heading": "Can I group or filter elements inside iframes or shadow DOM?",
      "heading_level": 3,
      "content_markdown": "### Can I group or filter elements inside iframes or shadow DOM?\n\nYes. 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "can-i-group-or-filter-elements-inside-iframes-or-shadow-dom"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 69
    },
    {
      "id": "ui-coverage/faq#why-isnt-my-element-group-showing-up-in-the-report",
      "doc_id": "ui-coverage/faq",
      "heading": "Why isn't my element group showing up in the report?",
      "heading_level": 3,
      "content_markdown": "### Why isn't my element group showing up in the report?\n\nThe most common causes are:\n\n*   An earlier `elementGroups` rule matches the same elements, and the first matching rule wins.\n*   The elements are excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), so they're never considered for grouping.\n*   The elements declare a group in markup with the `data-cy-ui-group` attribute, which takes priority over configuration rules.\n*   The selector matches a container rather than the interactive elements themselves.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-isnt-my-element-group-showing-up-in-the-report"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 123
    },
    {
      "id": "ui-coverage/faq#how-do-i-exclude-elements-from-ui-coverage",
      "doc_id": "ui-coverage/faq",
      "heading": "How do I exclude elements from UI Coverage?",
      "heading_level": 3,
      "content_markdown": "### How do I exclude elements from UI Coverage?\n\nAdd 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "how-do-i-exclude-elements-from-ui-coverage"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 87
    },
    {
      "id": "ui-coverage/faq#do-excluded-elements-count-toward-my-ui-coverage-score",
      "doc_id": "ui-coverage/faq",
      "heading": "Do excluded elements count toward my UI Coverage score?",
      "heading_level": 3,
      "content_markdown": "### Do excluded elements count toward my UI Coverage score?\n\nNo. 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.\n",
      "section": "ui-coverage",
      "anchors": [
        "do-excluded-elements-count-toward-my-ui-coverage-score"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 59
    },
    {
      "id": "ui-coverage/faq#why-isnt-my-elementfilters-rule-excluding-an-element",
      "doc_id": "ui-coverage/faq",
      "heading": "Why isn't my elementFilters rule excluding an element?",
      "heading_level": 3,
      "content_markdown": "### Why isn't my elementFilters rule excluding an element?\n\nThe most common causes are:\n\n*   The selector matches a container instead of the element itself. Filters use standard CSS matching against each tracked element, so `footer` matches only the `<footer>` element. Use a descendant selector like `footer *` to exclude everything inside a container.\n*   An earlier `elementFilters` rule already matched the element, and the first matching rule wins. An `include: true` rule above your exclude rule protects the elements it matches.\n*   The rule has a `documentScope` that doesn't match the element's iframe or shadow DOM hosts.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-isnt-my-elementfilters-rule-excluding-an-element"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 155
    },
    {
      "id": "ui-coverage/faq#can-i-exclude-elements-from-ui-coverage-without-affecting-cypress-accessibility",
      "doc_id": "ui-coverage/faq",
      "heading": "Can I exclude elements from UI Coverage without affecting Cypress Accessibility?",
      "heading_level": 3,
      "content_markdown": "### Can I exclude elements from UI Coverage without affecting Cypress Accessibility?\n\nYes. An `elementFilters` list at the root of your configuration applies to both products, but nesting it under a `uiCoverage` or `accessibility` key applies it to that product only. A nested list completely replaces a root-level one for that product; the two are not merged. See [Exclude elements](/llm/markdown/ui-coverage/configuration/elementfilters.md#Scope).\n",
      "section": "ui-coverage",
      "anchors": [
        "can-i-exclude-elements-from-ui-coverage-without-affecting-cypress-accessibility"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 80
    },
    {
      "id": "ui-coverage/faq#why-does-one-element-appear-as-multiple-elements-in-the-report",
      "doc_id": "ui-coverage/faq",
      "heading": "Why does one element appear as multiple elements in the report?",
      "heading_level": 3,
      "content_markdown": "### Why does one element appear as multiple elements in the report?\n\nThis usually means the element's identifying attributes change between [snapshots](/llm/markdown/ui-coverage/core-concepts/element-identification.md#Snapshots), for example auto-generated IDs or dynamic class names. Use [`attributeFilters`](/llm/markdown/ui-coverage/configuration/attributefilters.md) to ignore the dynamic attributes, or [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) to define the element's identity explicitly. See [troubleshooting](/llm/markdown/ui-coverage/troubleshooting.md) for more scenarios.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-does-one-element-appear-as-multiple-elements-in-the-report"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 67
    },
    {
      "id": "ui-coverage/faq#why-isnt-my-elements-rule-applying",
      "doc_id": "ui-coverage/faq",
      "heading": "Why isn't my elements rule applying?",
      "heading_level": 3,
      "content_markdown": "### Why isn't my elements rule applying?\n\nAn [`elements`](/llm/markdown/ui-coverage/configuration/elements.md) rule applies only when its selector matches exactly one interactive element in a snapshot. The most common causes are:\n\n*   The selector matches more than one interactive element in the same snapshot, so the rule is skipped for that snapshot. Add [`documentScope`](/llm/markdown/ui-coverage/configuration/elements.md#Options) or a more specific selector, or use [`elementGroups`](/llm/markdown/ui-coverage/configuration/elementgroups.md) if several elements should share an identity.\n*   The selector only matches non-interactive elements, such as a wrapper around the actual button or input.\n*   The element is excluded by [`elementFilters`](/llm/markdown/ui-coverage/configuration/elementfilters.md), so it's never considered.\n*   A later `elements` rule matches the same element, and the last matching rule wins.\n*   The report was processed before you saved the configuration. Regenerate the run to apply the current configuration.\n",
      "section": "ui-coverage",
      "anchors": [
        "why-isnt-my-elements-rule-applying"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 169
    },
    {
      "id": "ui-coverage/faq#configuration",
      "doc_id": "ui-coverage/faq",
      "heading": "Configuration",
      "heading_level": 2,
      "content_markdown": "## Configuration\n\n### Where do I set UI Coverage configuration?\n\nIn the **App Quality** tab of your project settings in Cypress Cloud. By default, only Admin users can edit configuration; your Cypress point-of-contact can change this on request. See [Setting configuration](/llm/markdown/ui-coverage/configuration/overview.md#Setting-configuration).\n\n### Do I need to rerun my tests after changing configuration?\n\nNo. You can regenerate any historical run from its **Properties** tab, and the report is reprocessed with the current configuration. This lets you iterate on configuration and see the effects immediately without running your Cypress tests again.\n\n### Can I use different configuration for different runs?\n\nYes. The [`profiles`](/llm/markdown/ui-coverage/configuration/profiles.md) property applies configuration overrides based on [run tags](/llm/markdown/app/references/command-line.md#cypress-run-tag-lt-tag-gt), so a smoke-test run and a full regression run can each use their own settings.\n",
      "section": "ui-coverage",
      "anchors": [
        "configuration"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 165
    },
    {
      "id": "ui-coverage/faq#where-do-i-set-ui-coverage-configuration",
      "doc_id": "ui-coverage/faq",
      "heading": "Where do I set UI Coverage configuration?",
      "heading_level": 3,
      "content_markdown": "### Where do I set UI Coverage configuration?\n\nIn the **App Quality** tab of your project settings in Cypress Cloud. By default, only Admin users can edit configuration; your Cypress point-of-contact can change this on request. See [Setting configuration](/llm/markdown/ui-coverage/configuration/overview.md#Setting-configuration).\n",
      "section": "ui-coverage",
      "anchors": [
        "where-do-i-set-ui-coverage-configuration"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 52
    },
    {
      "id": "ui-coverage/faq#do-i-need-to-rerun-my-tests-after-changing-configuration",
      "doc_id": "ui-coverage/faq",
      "heading": "Do I need to rerun my tests after changing configuration?",
      "heading_level": 3,
      "content_markdown": "### Do I need to rerun my tests after changing configuration?\n\nNo. You can regenerate any historical run from its **Properties** tab, and the report is reprocessed with the current configuration. This lets you iterate on configuration and see the effects immediately without running your Cypress tests again.\n",
      "section": "ui-coverage",
      "anchors": [
        "do-i-need-to-rerun-my-tests-after-changing-configuration"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 64
    },
    {
      "id": "ui-coverage/faq#can-i-use-different-configuration-for-different-runs",
      "doc_id": "ui-coverage/faq",
      "heading": "Can I use different configuration for different runs?",
      "heading_level": 3,
      "content_markdown": "### Can I use different configuration for different runs?\n\nYes. The [`profiles`](/llm/markdown/ui-coverage/configuration/profiles.md) property applies configuration overrides based on [run tags](/llm/markdown/app/references/command-line.md#cypress-run-tag-lt-tag-gt), so a smoke-test run and a full regression run can each use their own settings.\n",
      "section": "ui-coverage",
      "anchors": [
        "can-i-use-different-configuration-for-different-runs"
      ],
      "path": "/llm/json/chunked/ui-coverage/faq.json",
      "token_estimate": 47
    }
  ]
}