diff --git a/docs/accessibility/changelog.mdx b/docs/accessibility/changelog.mdx index a61eafbb3c..86b1d768d7 100644 --- a/docs/accessibility/changelog.mdx +++ b/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 diff --git a/docs/api/commands/get.mdx b/docs/api/commands/get.mdx index 0eee1f6a3e..667bfe7f54 100644 --- a/docs/api/commands/get.mdx +++ b/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 diff --git a/docs/app/continuous-integration/github-actions.mdx b/docs/app/continuous-integration/github-actions.mdx index c5199cd9ef..10cd1e654b 100644 --- a/docs/app/continuous-integration/github-actions.mdx +++ b/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. diff --git a/docs/app/continuous-integration/overview.mdx b/docs/app/continuous-integration/overview.mdx index 82c0ea1deb..a560f050ab 100644 --- a/docs/app/continuous-integration/overview.mdx +++ b/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 */} diff --git a/docs/app/faq.mdx b/docs/app/faq.mdx index 654f25636b..2b83a27624 100644 --- a/docs/app/faq.mdx +++ b/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 diff --git a/docs/app/guides/migration/protractor-to-cypress.mdx b/docs/app/guides/migration/protractor-to-cypress.mdx index 2ba1e27c0d..1a7821ea3a 100644 --- a/docs/app/guides/migration/protractor-to-cypress.mdx +++ b/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). Before: Protractor @@ -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? diff --git a/docs/app/references/changelog.mdx b/docs/app/references/changelog.mdx index a934017c8d..dd3f14a3d8 100644 --- a/docs/app/references/changelog.mdx +++ b/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 diff --git a/docs/app/references/configuration.mdx b/docs/app/references/configuration.mdx index 08ba5d93da..79bac1540a 100644 --- a/docs/app/references/configuration.mdx +++ b/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 diff --git a/docs/app/references/error-messages.mdx b/docs/app/references/error-messages.mdx index 3374eef281..c9eb89e89a 100644 --- a/docs/app/references/error-messages.mdx +++ b/docs/app/references/error-messages.mdx @@ -451,7 +451,7 @@ it('does not forget to return a promise', () => { Note 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 Note 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. ### `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: diff --git a/docs/app/references/troubleshooting.mdx b/docs/app/references/troubleshooting.mdx index 373a6e00d1..4cb2805adb 100644 --- a/docs/app/references/troubleshooting.mdx +++ b/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. diff --git a/docs/cloud/account-management/billing-and-usage.mdx b/docs/cloud/account-management/billing-and-usage.mdx index 7f4eb358e1..b783e3fcab 100644 --- a/docs/cloud/account-management/billing-and-usage.mdx +++ b/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 diff --git a/docs/partials/_anatomy-of-an-error.mdx b/docs/partials/_anatomy-of-an-error.mdx index d93f3180b3..4cc7138c8f 100644 --- a/docs/partials/_anatomy-of-an-error.mdx +++ b/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. diff --git a/docs/partials/_ci_provider_cloud_steps.mdx b/docs/partials/_ci_provider_cloud_steps.mdx index ddc535ebfa..bea5a7877f 100644 --- a/docs/partials/_ci_provider_cloud_steps.mdx +++ b/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 diff --git a/docs/partials/_document-domain-workaround.mdx b/docs/partials/_document-domain-workaround.mdx index b1972f97f4..bafb00c672 100644 --- a/docs/partials/_document-domain-workaround.mdx +++ b/docs/partials/_document-domain-workaround.mdx @@ -3,7 +3,7 @@ **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) diff --git a/docs/ui-coverage/changelog.mdx b/docs/ui-coverage/changelog.mdx index b9fcac957c..43d470f32d 100644 --- a/docs/ui-coverage/changelog.mdx +++ b/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