Merge branch 'main' into adding-descope-testing-strat-guide

Author: allenzhou101

docs/accessibility/changelog.mdx

@@ -17,7 +17,7 @@ sidebar_position: 200
 
 ## Week of 9/30/2024
 
-- Cypress Accessibility results are now included in Slack messages alongside test results. [Learn more about our Slack integration here](https://on.cypress.io/slack-integration).
+- Cypress Accessibility results are now included in Slack messages alongside test results. [Learn more about our Slack integration here](/cloud/integrations/slack).
 
 ## Week of 9/20/2024
 
@@ -34,7 +34,7 @@ sidebar_position: 200
 ## Week of 8/19/2024
 
 - iFrames are now supported for accessibility checks. iFrame processing is _opt-in_ for existing customers, but new customers will begin with iFrames enabled and can choose to opt out instead. This is to avoid disrupting existing pipelines, especially because iFrame content is not _always_ something you want to include in your reports.
-- Cypress Accessibility results will now appear in [GitHub](https://on.cypress.io/github-integration), [GitLab](https://on.cypress.io/gitlab-integration) and [Bitbucket](https://on.cypress.io/bitbucket-integration) pull request and merge request comments alongside test results. Integrations can be installed and comments can be enabled in Project Settings.
+- Cypress Accessibility results will now appear in [GitHub](/cloud/integrations/source-control/github), [GitLab](/cloud/integrations/source-control/gitlab) and [Bitbucket](/cloud/integrations/source-control/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/5/2024
 

docs/accessibility/core-concepts/how-it-works.mdx

@@ -43,4 +43,4 @@ In rare cases - such as if an Axe Core® update contains a critical security pat
 
 ## Powered by Test Replay
 
-Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject [Test Replay limitations](https://docs.cypress.io/faq/questions/cloud-faq#Is-everything-captured-and-replayed-in-Test-Replay).
+Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject to Test Replay limitations. Read [How Test Replay Works](/cloud/features/test-replay#How-Test-Replay-Works) to discover which data is captured and which browsers are supported.

docs/api/commands/get.mdx

@@ -146,9 +146,9 @@ cy.get('form').within(() => {
 ### Get vs Find
 
 The `cy.get` command always starts its search from the
-[cy.root](https://on.cypress.io/root) element. In most cases, it is the
+[cy.root](/api/commands/root) element. In most cases, it is the
 `document` element, unless used inside the [.within()](/api/commands/within)
-command. The [.find](https://on.cypress.io/find) command starts its search from
+command. The [.find](/api/commands/find) command starts its search from
 the current subject.
 
 ```html

docs/app/continuous-integration/github-actions.mdx

@@ -431,7 +431,7 @@ In the GitHub Actions configuration, we have defined in the previous section, we
 are leveraging three useful features of
 [Cypress Cloud](/cloud/get-started/introduction):
 
-1. [Recording test results with the `record: true` option](https://on.cypress.io/how-do-i-record-runs)
+1. [Recording test results with the `record: true` option](/cloud/get-started/setup)
    to [Cypress Cloud](https://on.cypress.io/cloud):
 
    - In-depth and shareable
@@ -540,7 +540,7 @@ jobs:
 :::tip
 
 We also recommend adding `COMMIT_INFO_SHA` to re-enable
-[Cypress bot PR comments](https://on.cypress.io/github#Pull-request-comments).
+[Cypress bot PR comments](/cloud/integrations/source-control/github#Pull-request-comments).
 See
 [this comment](https://github.com/cypress-io/github-action/issues/124#issuecomment-716584972)
 for more details.

docs/app/continuous-integration/overview.mdx

@@ -352,7 +352,7 @@ Cypress:**
 - The browser crashes.
 
 You can see the total available machine memory and the current free memory by
-running the [`cypress info`](https://on.cypress.io/command-line#cypress-info)
+running the [`cypress info`](/app/references/command-line#cypress-info)
 command.
 
 {/* hack: using css language label to respect decimals in syntax highlighting */}

docs/app/faq.mdx

@@ -90,7 +90,7 @@ application, it helps you write your tests.
 There is a plugin and detailed documentation on how to get end-to-end, unit and
 full stack code coverage.
 
-- Read our [Code Coverage guide](https://on.cypress.io/code-coverage)
+- Read our [Code Coverage guide](/app/tooling/code-coverage)
 - Use the [@cypress/code-coverage](https://github.com/cypress-io/code-coverage)
   plugin
 

docs/app/guides/migration/protractor-to-cypress.mdx

@@ -311,7 +311,7 @@ When it comes to e2e tests, one of the most common things you'll need to do is
 get one or more HTML elements on a page. Rather than split element fetching into
 multiple methods that you need to memorize, everything can be accomplished with
 [`cy.get`](/api/commands/get) while using CSS selectors or the preferred
-[**data attribute**](https://on.cypress.io/selecting-elements).
+[**data attribute**](/app/core-concepts/best-practices#Selecting-Elements).
 
 <Badge type="danger">Before: Protractor</Badge>
 
@@ -1217,7 +1217,7 @@ Read our docs to learn more about speeding up test execution in CI via
 As you write more and more end-to-end tests, you will find yourself wondering -
 do I need to write more tests? Are there parts of the application still
 untested? Are there parts of the application that perhaps are tested too much?
-This [code coverage guide](https://on.cypress.io/code-coverage) is an excellent
+This [code coverage guide](/app/tooling/code-coverage) is an excellent
 resource to learn how to add code coverage.
 
 ### Questions or Issues?

docs/app/references/changelog.mdx

@@ -1030,7 +1030,7 @@ _Released 04/26/2023_
 - Added Component Testing support for Angular 16. Addresses
   [#26044](https://github.com/cypress-io/cypress/issues/26044).
 - The run navigation component on the
-  [Debug page](https://on.cypress.io/debug-page) will now display a warning
+  [Debug page](/app/core-concepts/open-mode#Debug) will now display a warning
   message if there are more relevant runs than can be displayed in the list.
   Addresses [#26288](https://github.com/cypress-io/cypress/issues/26288).
 
@@ -1040,7 +1040,7 @@ _Released 04/26/2023_
   output to be broken. `0` is now treated as false. Addresses
   [#5191](https://github.com/cypress-io/cypress/issues/5191) and
   [#24595](https://github.com/cypress-io/cypress/issues/24595).
-- Fixed an issue on the [Debug page](https://on.cypress.io/debug-page) where the
+- Fixed an issue on the [Debug page](/app/core-concepts/open-mode#Debug) where the
   passing run status would appear even if the Cypress Cloud organization was
   over its monthly test result limit. Addresses
   [#26528](https://github.com/cypress-io/cypress/issues/26528).
@@ -1064,7 +1064,7 @@ _Released 04/17/2023_
 
 - The Component Testing setup wizard will now show a warning message if an issue
   is encountered with an installed
-  [third party framework definition](https://on.cypress.io/component-integrations).
+  [third party framework definition](/app/component-testing/custom-frameworks).
   Addresses [#25838](https://github.com/cypress-io/cypress/issues/25838).
 
 **Bugfixes:**
@@ -1310,7 +1310,7 @@ _Released 02/15/2023_
   Enterprise plans the flexibility to alter the auto-cancellation value per run.
   Addressed in [#25237](https://github.com/cypress-io/cypress/pull/25237).
 - It is now possible to overwrite query commands using
-  [`Cypress.Commands.overwriteQuery`](https://on.cypress.io/api/custom-queries).
+  [`Cypress.Commands.overwriteQuery`](/api/cypress-api/custom-queries).
   Addressed in [#25078](https://github.com/cypress-io/cypress/issues/25078).
 - Added [`Cypress.require()`](/api/cypress-api/require) for including
   dependencies within the [`cy.origin()`](/api/commands/origin) callback. This
@@ -4486,9 +4486,9 @@ _Released 06/23/2021_
 **Features:**
 
 - You can now override the default delay between typing characters for `.type()`
-  with [`Cypress.Keyboard.defaults()`](https://on.cypress.io/keyboard-api) or
+  with [`Cypress.Keyboard.defaults()`](/api/cypress-api/keyboard-api) or
   via
-  [test configuration](https://on.cypress.io/writing-and-organizing-tests#Allowed-config-values).
+  [test configuration](/app/core-concepts/writing-and-organizing-tests#Allowed-config-values).
   Addresses [#566](https://github.com/cypress-io/cypress/issues/566).
 - The experience when opening a new project via `cypress open` has been
   improved. Addressed in

docs/app/references/configuration.mdx

@@ -40,7 +40,7 @@ syntax, which is the default for JavaScript files. All JavaScript config
 examples in our docs use the CommonJS format.
 
 If you [configure your tests to record](/cloud/get-started/setup#Setup) the
-results to [Cypress Cloud](https://on.cypress.io/cloud-introduction) the
+results to [Cypress Cloud](/cloud/get-started/introduction) the
 `projectId` will be stored in the config file as well.
 
 ## Intelligent Code Completion

docs/app/references/error-messages.mdx

@@ -451,7 +451,7 @@ it('does not forget to return a promise', () => {
 <strong>Note</strong>
 
 This error only pertains to Cypress version `v11.0.0` and under. As of Cypress
-[v12.0.0](https://on.cypress.io/changelog#12-0-0), users can navigate to
+[v12.0.0](/app/references/changelog#12-0-0), users can navigate to
 multiple domains in a single test.
 
 :::
@@ -465,7 +465,7 @@ See our [Cross Origin Testing](/app/guides/cross-origin-testing#Limitations) doc
 <strong>Note</strong>
 
 This error only pertains to Cypress version `v11.0.0` and under. As of Cypress
-[v12.0.0](https://on.cypress.io/changelog#12-0-0), users can navigate to
+[v12.0.0](/app/references/changelog#12-0-0), users can navigate to
 multiple domains in a single test.
 
 :::
@@ -485,7 +485,7 @@ for more information and workarounds.
 
 ### <Icon name="exclamation-triangle" color="red" /> `cy.visit()` succeeded, but commands are timing out
 
-As of Cypress [v12.0.0](https://on.cypress.io/changelog#12-0-0), users can
+As of Cypress [v12.0.0](/app/references/changelog#12-0-0), users can
 navigate to multiple domains in a single test. The following test will succeed
 as-is:
 
@@ -851,7 +851,7 @@ regedit or gpedit.
 The `--auto-cancel-after-failures` flag is only available in Cypress 12.6.0 and
 later, and must be used with the `cypress run` command.
 
-### <Icon name="exclamation-triangle" color="red" /> --auto-cancel-after-failures must be a integer or false
+### <Icon name="exclamation-triangle" color="red" /> --auto-cancel-after-failures must be an integer or false
 
 You passed in an invalid value for the `--auto-cancel-after-failures` flag. It
 must be an integer or false.
@@ -869,8 +869,7 @@ Cancellation.
 You passed the `--auto-cancel-after-failures` flag, but this run originally
 started with a different value on this `--auto-cancel-after-failures` flag.
 
-The first setting of `--auto-cancel-after-failures` for any given run takes
-precedent.
+The first setting of `--auto-cancel-after-failures` for any given run takes precedence.
 
 ## Page Load Errors
 

docs/app/references/troubleshooting.mdx

@@ -90,7 +90,7 @@ You can check the current company policies for your Chrome installation by typin
 ### Allow Cypress URLs on VPNs
 
 To send the data and results of your tests to
-[Cypress Cloud](https://on.cypress.io/cloud-introduction), Cypress needs free
+[Cypress Cloud](/cloud/get-started/introduction), Cypress needs free
 access to some URLs.
 
 <UrlAllowList />

docs/cloud/account-management/billing-and-usage.mdx

@@ -31,12 +31,12 @@ To qualify, all Projects in
 your Organization must meet the following criteria:
 
 - Be a non-commercial entity
-- Be [Public](https://on.cypress.io/projects#Change-project-access) in Cypress
+- Be [Public](/cloud/account-management/projects#Change-project-access) in Cypress
   Cloud
 - Your Project source code is available in a public location with an
   [OSI-approved license](https://opensource.org/licenses)
 - Record minimum of 500
-  [tests](https://on.cypress.io/cloud-faq#What-counts-as-a-test-result) included
+  [tests](/cloud/faq#What-counts-as-a-test-result) included
   with the [Starter Plan](https://www.cypress.io/pricing)
 
 ### Requesting OSS plan for an Org

docs/partials/_anatomy-of-an-error.mdx

@@ -11,14 +11,14 @@ Cypress test.
 4. **Code frame file**: This is usually the top line of the stack trace and it
    shows the file, line number, and column number that is highlighted in the
    code frame below. Clicking on this link will open the file in your
-   [preferred file opener](https://on.cypress.io/IDE-integration#File-Opener-Preference)
+   [preferred file opener](/app/tooling/IDE-integration#File-Opener-Preference)
    and highlight the line and column in editors that support it.
 5. **Code frame**: This shows a snippet of code where the failure occurred, with
    the relevant line and column highlighted.
 6. **View stack trace**: Clicking this toggles the visibility of the stack
    trace. Stack traces vary in length. Clicking on a blue file path will open
    the file in your
-   [preferred file opener](https://on.cypress.io/IDE-integration#File-Opener-Preference).
+   [preferred file opener](/app/tooling/IDE-integration#File-Opener-Preference).
 7. **Print to console button**: Click this to print the full error to your
    DevTools console. This will usually allow you to click on lines in the stack
    trace and open files in your DevTools.

docs/partials/_ci_provider_cloud_steps.mdx

@@ -5,7 +5,7 @@ https://github.com/facebook/docusaurus/issues/3915
 TODO: reuse this bulk of text for now until the Docusaurus v3 refactor.
 -->
 
-1. [Recording test results with the `--record` flag](https://on.cypress.io/how-do-i-record-runs)
+1. [Recording test results with the `--record` flag](/cloud/get-started/setup)
    to Cypress Cloud.
 
    - In-depth and shareable

docs/partials/_document-domain-workaround.mdx

@@ -3,7 +3,7 @@
 <Icon name="exclamation-triangle" /> **Disabling document.domain Injection**
 
 In some cases, `document.domain` injection may cause issues. As of Cypress
-[v12.4.0](https://on.cypress.io/changelog#12-4-0), disabling `document.domain`
+[v12.4.0](/app/references/changelog#12-4-0), disabling `document.domain`
 injection is available with the `experimentalSkipDomainInjection` option. Please
 read about this
 [experiment](/app/references/experiments#Experimental-Skip-Domain-Injection)

docs/ui-coverage/changelog.mdx

@@ -13,7 +13,7 @@ sidebar_position: 200
 
 ## 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](https://on.cypress.io/slack-integration).
+- **Slack Messages:** UI Coverage results results are now included in Slack messages alongside test results. [Learn more about our Slack integration here](/cloud/integrations/slack).
 
 ## Week of 9/23/2024
 
@@ -26,7 +26,7 @@ sidebar_position: 200
 ## Week of 8/19/2024
 
 - **Results API:** We have added the new [Results API](/ui-coverage/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](https://on.cypress.io/github-integration), [GitLab](https://on.cypress.io/gitlab-integration) and [Bitbucket](https://on.cypress.io/bitbucket-integration) pull request and merge request comments alongside test results. Integrations can be installed and comments can be enabled in Project Settings.
+- **Pull and Merge Request Comments:** UI Coverage results will now appear in [GitHub](/cloud/integrations/source-control/github), [GitLab](/cloud/integrations/source-control/gitlab) and [Bitbucket](/cloud/integrations/source-control/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
 

docs/ui-coverage/core-concepts/interactivity.mdx

@@ -36,3 +36,23 @@ UI Coverage considers interactive elements "tested" if they are interacted with
 - `trigger`
 - `type`
 - `uncheck`
+
+## Untested Links
+
+UI Coverage tracks links (`<a>` elements) that haven't been visited during testing. For each untested link, you can see:
+
+### Referrers
+
+The Views containing links to this untested destination. This helps you understand:
+
+- Where these untested areas are referenced from
+- The navigation paths that could lead to this untested area
+- The context in which these links appear
+
+### URLs
+
+Shows how similar URLs are grouped together. For example, if you have links to `/users/1`, `/users/2`, and `/users/3`, they'll be grouped as `/users/*`. The URLs section shows all the actual URLs that were grouped together. This is particularly useful for:
+
+- Understanding the scope of dynamic routes in your application
+- Seeing how many variations of a URL pattern exist
+- Writing configuration rules to handle URL patterns appropriately

docs/ui-coverage/core-concepts/views.mdx

@@ -9,14 +9,30 @@ sidebar_position: 100
 
 <UICovAddon />
 
-UI Coverage is organized into views, which are the unique URLs across all snapshots from end-to-end tests and the unique mounted components from component tests.
+UI Coverage organizes all unique URLs across snapshots from end-to-end tests and mounted components from component tests into "Views". A View represents a distinct page or state in your application.
 
-### Grouping
+## View Creation & Grouping
 
-UI Coverage uses certain default rules to generate a single view from dynamic URLs that represent the same page:
+By default, UI Coverage uses certain rules to generate a single View from dynamic URLs that represent the same page:
 
-- All search parameters are removed.
-- All hash parameters are removed, unless the hash parameter starts with a `/`, such as `#/admin`.
-- If there are multiple URLs that are exactly the same except for a different integer or UUID value in the same path parameter, then that path parameter is replaced with a wildcard (`*`).
+- All search parameters are removed
+- Hash parameters are removed (unless they start with `/`, such as `#/admin`)
+- If multiple URLs differ only by an integer or UUID in the same path parameter, that parameter is replaced with a wildcard (`*`)
 
-These rules can be overridden via [views](/ui-coverage/configuration/views) configuration.
+For example:
+
+- `/users/123/profile` and `/users/456/profile` would be grouped into `/users/*/profile`
+- `/dashboard?tab=overview` and `/dashboard?tab=settings` would be grouped into `/dashboard`
+- `/app#settings` and `/app#profile` would be grouped into `/app`
+- `/app#/admin` and `/app#/settings` would remain separate Views
+
+## Using Views
+
+In the UI Coverage interface, Views are listed with their coverage scores, helping you:
+
+- See which areas of your application have been tested
+- Identify untested pages and components
+- Track changes in coverage across different parts of your application
+- Focus testing efforts on critical paths and flows
+
+You can customize how URLs are grouped into Views using [views](/ui-coverage/configuration/views) and [viewFilters](/ui-coverage/configuration/viewfilters) configuration options.

docs/ui-coverage/get-started/introduction.mdx

@@ -54,4 +54,4 @@ UI Coverage captures "snapshots" of every page visited by your Cypress tests (an
 
 As a result, a UI Coverage score is generated. This score quantifies coverage across your application by measuring the ratio of the unique elements that have been tested to the total unique elements that are found across your application.
 
-Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject to any [limitations of Test Replay](https://docs.cypress.io/faq/questions/cloud-faq#Is-everything-captured-and-replayed-in-Test-Replay) data captured and browser support.
+Because Cypress UI Coverage uses data captured through Cypress Test Replay, it is subject to Test Replay limitations. Read [How Test Replay Works](/cloud/features/test-replay#How-Test-Replay-Works) to discover which data is captured and which browsers are supported.