From 00e5ba0c55877d88fbe0e7b9eb5aa350662ecfae Mon Sep 17 00:00:00 2001 From: Chris Breiding Date: Mon, 12 Apr 2021 14:39:56 -0400 Subject: [PATCH 1/2] 7.1.0 changelog --- content/_changelogs/7.1.0.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 content/_changelogs/7.1.0.md diff --git a/content/_changelogs/7.1.0.md b/content/_changelogs/7.1.0.md new file mode 100644 index 0000000000..4636a9b62a --- /dev/null +++ b/content/_changelogs/7.1.0.md @@ -0,0 +1,14 @@ +## 7.1.0 + +_Released 04/12/2021_ + +**Features:** + +- The events `before:spec`, `after:spec`, `before:run`, and `after:run` now fire in interactive mode in addition to run mode. This requires the `experimentalInteractiveRunEvents` flag to be enabled. Addressed in [#15787](https://github.com/cypress-io/cypress/pull/15787). + +**Bugfixes:** + +- Viewport configuration set in `cypress.json` is now correctly applied in the Component Test Runner. Fixes [#15899](https://github.com/cypress-io/cypress/issues/15899). +- Running specs on Windows is now supported in the Component Test Runner. Fixes [#15842](https://github.com/cypress-io/cypress/issues/15842). +- Fixed an issue where crashes in Cypress would cause a misleading "Unknown signal: true" error after the actual crash message. Fixes [#15943](https://github.com/cypress-io/cypress/issues/15943). +- Fixed an issue introduced in 7.0.0 where requests with responses stubbed via `cy.intercept(routeMatcher, staticResponse)` would still be sent to the destination server. Fixes [#15841](https://github.com/cypress-io/cypress/issues/15841). From e5b8345e3a664140ae315a37dbedff3767a52a8b Mon Sep 17 00:00:00 2001 From: Chris Breiding Date: Mon, 12 Apr 2021 15:43:31 -0400 Subject: [PATCH 2/2] feat: Update run events pages with interactive mode details (#3791) --- content/_changelogs/3.8.1.md | 2 +- content/_changelogs/6.7.0.md | 2 +- content/api/plugins/after-run-api.md | 21 ++++++-- content/api/plugins/after-screenshot-api.md | 2 +- content/api/plugins/after-spec-api.md | 14 ++++-- content/api/plugins/before-run-api.md | 48 ++++++++++++++----- content/api/plugins/before-spec-api.md | 10 +++- content/api/plugins/browser-launch-api.md | 4 +- content/api/plugins/configuration-api.md | 6 +-- content/api/plugins/preprocessors-api.md | 2 +- content/api/plugins/writing-a-plugin.md | 2 +- .../writing-and-organizing-tests.md | 6 +-- content/guides/references/configuration.md | 2 +- content/guides/references/experiments.md | 12 +++-- content/guides/references/migration-guide.md | 2 +- content/guides/references/troubleshooting.md | 2 +- content/guides/tooling/plugins-guide.md | 4 +- scripts/partials.js | 4 +- 18 files changed, 98 insertions(+), 47 deletions(-) diff --git a/content/_changelogs/3.8.1.md b/content/_changelogs/3.8.1.md index 0a91ba7dd0..47fd954b64 100644 --- a/content/_changelogs/3.8.1.md +++ b/content/_changelogs/3.8.1.md @@ -8,7 +8,7 @@ _Released 12/26/2019_ - We fixed an issue where, on some systems with IPv4 and IPv6 enabled, Cypress would fail to connect to the Chrome DevTools Protocol while launching Chrome, leading to test failures. Fixes [#5912](https://github.com/cypress-io/cypress/issues/5912). - The strict cookie validation added in [3.5.0](#3-5-0) for [cy.setCookie()](/api/commands/setcookie), [cy.clearCookie()](/api/commands/clearcookie), and [cy.getCookie()](/api/commands/getcookie) has been removed. Fixes [#5642](https://github.com/cypress-io/cypress/issues/5642). - We fixed a regression in [3.8.0](#3-8-0) where using [.type()](/api/commands/type) on number inputs to type non-number characters or the `{enter}` special character would not type the correct value. Fixes [#5968](https://github.com/cypress-io/cypress/issues/5968) and [#5997](https://github.com/cypress-io/cypress/issues/5997). -- Configuration values set from the plugin file now display with the correct background color in the Configuration panel in the Test Runner Settings. Fixes [#6024](https://github.com/cypress-io/cypress/issues/6024). +- Configuration values set from the plugins file now display with the correct background color in the Configuration panel in the Test Runner Settings. Fixes [#6024](https://github.com/cypress-io/cypress/issues/6024). - We removed the 'Me' and 'An Organization' selections in the Test Runner when setting up a project to more closely match the Dashboard UI. This also fixes an edge case where a user with no default organizations could potentially be unable to set up a project. Fixes [#5954](https://github.com/cypress-io/cypress/issues/5954). **Misc:** diff --git a/content/_changelogs/6.7.0.md b/content/_changelogs/6.7.0.md index 5d1ad251da..540d2a8738 100644 --- a/content/_changelogs/6.7.0.md +++ b/content/_changelogs/6.7.0.md @@ -25,7 +25,7 @@ _Released 3/15/2021_ - We updated the UI when connecting a project to the Dashboard. Addressed in [#14877](https://github.com/cypress-io/cypress/issues/14877). - "Test recordings" recorded to the Cypress Dashboard are now referred to as recorded "test results." Addresses [#15376](https://github.com/cypress-io/cypress/issues/15376). -- Errors shown from plugins files now display top-aligned. Addressed in [#15347](https://github.com/cypress-io/cypress/issues/15347). +- Errors shown from the plugins file now display top-aligned. Addressed in [#15347](https://github.com/cypress-io/cypress/issues/15347). **Dependency Updates:** diff --git a/content/api/plugins/after-run-api.md b/content/api/plugins/after-run-api.md index 55b871501b..4b72227082 100644 --- a/content/api/plugins/after-run-api.md +++ b/content/api/plugins/after-run-api.md @@ -2,15 +2,21 @@ title: After Run API --- -The `after:run` event fires after a run is finished. The event only fires when running via `cypress run`. +The `after:run` event fires after a run is finished. When running cypress via `cypress open`, the event will fire when closing a project. -The event will fire each time `cypress run` executes. As a result, if running your specs in [parallel](/guides/guides/parallelization), the event will fire once for each machine on which `cypress run` is called. +When running via `cypress run`, the event will fire each time `cypress run` executes. As a result, if running your specs in [parallel](/guides/guides/parallelization), the event will fire once for each machine on which `cypress run` is called. ## Syntax -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. + + + + + +⚠️ When running via `cypress open`, the `after:run` event only fires if the [experimentalInteractiveRunEvents flag](/guides/references/configuration#Experiments) is enabled. @@ -24,6 +30,8 @@ on('after:run', (results) => { Results of the run, including the total number of passes/failures/etc, the project config, and details about the browser and system. It is the same as the results object resolved by the [Module API](/guides/guides/module-api#Results). +Results are only provided when running via `cypress run`. When running via `cypress open`, the results will be undefined. + ## Usage You can return a promise from the `after:run` event handler and it will be awaited before Cypress proceeds running your specs. @@ -33,7 +41,7 @@ You can return a promise from the `after:run` event handler and it will be await ```javascript module.exports = (on, config) => { on('after:run', (results) => { - // results will look something like this: + // results will look something like this when run via `cypress run`: // { // totalDuration: 81, // totalSuites: 0, @@ -58,7 +66,10 @@ module.exports = (on, config) => { // } // } - console.log(results.totalPassed, 'out of', results.totalTests, 'passed') + if (results) { + // results will be undefined in interactive mode + console.log(results.totalPassed, 'out of', results.totalTests, 'passed') + } }) } ``` diff --git a/content/api/plugins/after-screenshot-api.md b/content/api/plugins/after-screenshot-api.md index ed7be85010..39bf4a924a 100644 --- a/content/api/plugins/after-screenshot-api.md +++ b/content/api/plugins/after-screenshot-api.md @@ -10,7 +10,7 @@ This allows you to record those details, manipulate the image as needed, and ret -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/content/api/plugins/after-spec-api.md b/content/api/plugins/after-spec-api.md index faf12d3167..2f457be3ec 100644 --- a/content/api/plugins/after-spec-api.md +++ b/content/api/plugins/after-spec-api.md @@ -2,13 +2,19 @@ title: After Spec API --- -The `after:spec` event fires after a spec file is run. The event only fires when running via `cypress run`. +The `after:spec` event fires after a spec file is run. When running cypress via `cypress open`, the event will fire when the browser closes. ## Syntax -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. + + + + + +⚠️ When running via `cypress open`, the `after:spec` event only fires if the [experimentalInteractiveRunEvents flag](/guides/references/configuration#Experiments) is enabled. @@ -32,6 +38,8 @@ Details of the spec file, including the following properties: Details of the spec file's results, including numbers of passes/failures/etc and details on the tests themselves. +Results are only provided when running via `cypress run`. When running via `cypress open`, the results will be undefined. + ## Usage You can return a promise from the `after:spec` event handler and it will be awaited before Cypress proceeds with processing the spec's video or moving on to further specs if there are any. @@ -91,7 +99,7 @@ const del = require('del') module.exports = (on, config) => { on('after:spec', (spec, results) => { - if (results.stats.failures === 0 && results.video) { + if (results && results.stats.failures === 0 && results.video) { // `del()` returns a promise, so it's important to return it to ensure // deleting the video is finished before moving on return del(results.video) diff --git a/content/api/plugins/before-run-api.md b/content/api/plugins/before-run-api.md index 1efc404711..24ac03937a 100644 --- a/content/api/plugins/before-run-api.md +++ b/content/api/plugins/before-run-api.md @@ -2,7 +2,7 @@ title: Before Run API --- -The `before:run` event fires before a run starts. The event only fires when running via `cypress run`. +The `before:run` event fires before a run starts. When running cypress via `cypress open`, the event will fire when opening a project. The event will fire each time `cypress run` executes. As a result, if running your specs in [parallel](/guides/guides/parallelization), the event will fire once for each machine on which the tests are run. @@ -10,7 +10,13 @@ The event will fire each time `cypress run` executes. As a result, if running yo -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. + + + + + +⚠️ When running via `cypress open`, the `before:run` event only fires if the [experimentalInteractiveRunEvents flag](/guides/references/configuration#Experiments) is enabled. @@ -22,7 +28,7 @@ on('before:run', (details) => { ** details** **_(Object)_** -Details of the run, including the project config, details about the browser and system, and the specs that will be run. +Details of the run, including the project config, system information, and the version of Cypress. More details are included when running via `cypress run`. ## Usage @@ -33,7 +39,7 @@ You can return a promise from the `before:run` event handler and it will be awai ```javascript module.exports = (on, config) => { on('before:run', (details) => { - // details will look something like this: + // details will look something like this when run via `cypress run`: // { // config: { // projectId: '12345', @@ -47,8 +53,7 @@ module.exports = (on, config) => { // version: '59.0.3071.115', // // ...more properties... // }, - // system: - // { + // system: { // osName: 'darwin', // osVersion: '16.7.0', // } @@ -69,12 +74,31 @@ module.exports = (on, config) => { // tag: 'tag-1' // } - console.log( - 'Running', - details.specs.length, - 'specs in', - details.browser.name - ) + // details will look something like this when run via `cypress open`: + // { + // config: { + // projectId: '12345', + // baseUrl: 'http://example.com/', + // viewportWidth: 1000, + // viewportHeight: 660, + // // ...more properties... + // }, + // system: { + // osName: 'darwin', + // osVersion: '16.7.0', + // } + // cypressVersion: '7.0.0' + // } + + if (details.specs && details.browser) { + // details.specs and details.browser will be undefined in interactive mode + console.log( + 'Running', + details.specs.length, + 'specs in', + details.browser.name + ) + } }) } ``` diff --git a/content/api/plugins/before-spec-api.md b/content/api/plugins/before-spec-api.md index 5e4207efb7..a91febd782 100644 --- a/content/api/plugins/before-spec-api.md +++ b/content/api/plugins/before-spec-api.md @@ -2,13 +2,19 @@ title: Before Spec API --- -The `before:spec` event fires before a spec file is run. The event only fires when running via `cypress run`. +The `before:spec` event fires before a spec file is run. When running cypress via `cypress open`, the event will fire when the browser launches. ## Syntax -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. + + + + + +⚠️ When running via `cypress open`, the `before:spec` event only fires if the [experimentalInteractiveRunEvents flag](/guides/references/configuration#Experiments) is enabled. diff --git a/content/api/plugins/browser-launch-api.md b/content/api/plugins/browser-launch-api.md index 1f8fbddac6..af9a544847 100644 --- a/content/api/plugins/browser-launch-api.md +++ b/content/api/plugins/browser-launch-api.md @@ -8,13 +8,13 @@ Before Cypress launches a browser, it gives you the opportunity to modify the br -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/content/api/plugins/configuration-api.md b/content/api/plugins/configuration-api.md index a10dfbf2b4..5c30200a11 100644 --- a/content/api/plugins/configuration-api.md +++ b/content/api/plugins/configuration-api.md @@ -2,19 +2,19 @@ title: Configuration API --- -Cypress enables you to dynamically modify configuration values and environment variables from your plugin file. +Cypress enables you to dynamically modify configuration values and environment variables from your plugins file. ## Usage -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/content/api/plugins/preprocessors-api.md b/content/api/plugins/preprocessors-api.md index 9a979cf28d..b5d19a2de9 100644 --- a/content/api/plugins/preprocessors-api.md +++ b/content/api/plugins/preprocessors-api.md @@ -51,7 +51,7 @@ If you don't use webpack in your project or would like to keep the majority of t -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/content/api/plugins/writing-a-plugin.md b/content/api/plugins/writing-a-plugin.md index f0cfdbce36..09e0be564d 100644 --- a/content/api/plugins/writing-a-plugin.md +++ b/content/api/plugins/writing-a-plugin.md @@ -31,7 +31,7 @@ module.exports = (on, config) => { -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/content/guides/core-concepts/writing-and-organizing-tests.md b/content/guides/core-concepts/writing-and-organizing-tests.md index 0bc3029d30..3b308fc2ff 100644 --- a/content/guides/core-concepts/writing-and-organizing-tests.md +++ b/content/guides/core-concepts/writing-and-organizing-tests.md @@ -146,11 +146,11 @@ Any videos recorded of the run are stored in the [`videosFolder`](/guides/refere To learn more about videos and settings available, see [Screenshots and Videos](/guides/guides/screenshots-and-videos#Screenshots) -### Plugin files +### Plugins file -The plugin file is a special file that executes in Node before the project is loaded, before the browser launches, and during your test execution. While the Cypress tests execute in the browser, the plugin file runs in the background Node process, giving your tests the ability to access the file system and the rest of the operating system by calling the [cy.task()](/api/commands/task) command. +The plugins file is a special file that executes in Node before the project is loaded, before the browser launches, and during your test execution. While the Cypress tests execute in the browser, the plugins file runs in the background Node process, giving your tests the ability to access the file system and the rest of the operating system by calling the [cy.task()](/api/commands/task) command. -The plugin file is a good place to define how you want to bundle the spec files via the [preprocessors](/api/plugins/preprocessors-api), how to find and launch the browsers via the [browser launch API](/api/plugins/browser-launch-api), and other cool things. Read our [plugins guide](/guides/tooling/plugins-guide) for more details and examples. +The plugins file is a good place to define how you want to bundle the spec files via the [preprocessors](/api/plugins/preprocessors-api), how to find and launch the browsers via the [browser launch API](/api/plugins/browser-launch-api), and other cool things. Read our [plugins guide](/guides/tooling/plugins-guide) for more details and examples. The initial imported plugins file can be [configured to another file](/guides/references/configuration#Folders-Files). diff --git a/content/guides/references/configuration.md b/content/guides/references/configuration.md index 6b541ba229..a0dda57730 100644 --- a/content/guides/references/configuration.md +++ b/content/guides/references/configuration.md @@ -344,7 +344,7 @@ When you open a Cypress project, clicking on the **Settings** tab will display t - The [Cypress environment file](/guides/guides/environment-variables#Option-2-cypress-env-json) - System [environment variables](/guides/guides/environment-variables#Option-3-CYPRESS) - [Command Line arguments](/guides/guides/command-line) -- [Plugin file](/api/plugins/configuration-api) +- [Plugins file](/api/plugins/configuration-api) diff --git a/content/guides/references/experiments.md b/content/guides/references/experiments.md index 5ed67b4ad1..d0b7e34389 100644 --- a/content/guides/references/experiments.md +++ b/content/guides/references/experiments.md @@ -14,16 +14,18 @@ If you'd like to try out what we're working on in the [Test Runner](/guides/core You can pass the [configuration](/guides/references/configuration) options below to enable or disable experiments. See our [Configuration Guide](/guides/references/configuration) on how to pass configuration to Cypress. -| Option | Default | Description | -| ----------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `experimentalFetchPolyfill` | `false` | Automatically replaces `window.fetch` with a polyfill that Cypress can spy on and stub. Note: `experimentalFetchPolyfill` has been deprecated in Cypress 6.0.0 and will be removed in a future release. Consider using [cy.intercept()](/api/commands/intercept) to intercept `fetch` requests instead. | -| `experimentalSourceRewriting` | `false` | Enables AST-based JS/HTML rewriting. This may fix issues caused by the existing regex-based JS/HTML replacement algorithm. See [#5273](https://github.com/cypress-io/cypress/issues/5273) for details. | -| `experimentalStudio` | `false` | Generate and save commands directly to your test suite by interacting with your app as an end user would. See [Cypress Studio](/guides/core-concepts/cypress-studio) for more details. | +| Option | Default | Description | +| ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `experimentalFetchPolyfill` | `false` | Automatically replaces `window.fetch` with a polyfill that Cypress can spy on and stub. Note: `experimentalFetchPolyfill` has been deprecated in Cypress 6.0.0 and will be removed in a future release. Consider using [cy.intercept()](/api/commands/intercept) to intercept `fetch` requests instead. | +| `experimentalInteractiveRunEvents` | `false` | Allows listening to the [`before:run`](/api/plugins/before-run-api), [`after:run`](/api/plugins/after-run-api), [`before:spec`](/api/plugins/before-spec-api), and [`after:spec`](/api/plugins/after-spec-api) events in the plugins file during interactive mode. | +| `experimentalSourceRewriting` | `false` | Enables AST-based JS/HTML rewriting. This may fix issues caused by the existing regex-based JS/HTML replacement algorithm. See [#5273](https://github.com/cypress-io/cypress/issues/5273) for details. | +| `experimentalStudio` | `false` | Generate and save commands directly to your test suite by interacting with your app as an end user would. See [Cypress Studio](/guides/core-concepts/cypress-studio) for more details. | ## History | Version | Changes | | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | +| [7.1.0](/guides/references/changelog#6-3-0) | Added support for `experimentalInteractiveRunEvents`. | | [7.0.0](/guides/references/changelog#7-0-0) | Removed `experimentalComponentTesting` and made it the default behavior. | | [6.7.0](/guides/references/changelog#6-7-0) | Removed `experimentalRunEvents` and made it the default behavior. | | [6.3.0](/guides/references/changelog#6-3-0) | Added support for `experimentalStudio`. | diff --git a/content/guides/references/migration-guide.md b/content/guides/references/migration-guide.md index d61130e093..0f628d3323 100644 --- a/content/guides/references/migration-guide.md +++ b/content/guides/references/migration-guide.md @@ -1175,7 +1175,7 @@ apt-get install libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 lib ### TypeScript esModuleInterop -Cypress no longer forces the `esModuleInterop` compiler option for TypeScript to be `true` for spec, support, and plugin files. We recommend setting it in your project's `tsconfig.json` instead if you need to. +Cypress no longer forces the `esModuleInterop` compiler option for TypeScript to be `true` for spec, support, and plugins files. We recommend setting it in your project's `tsconfig.json` instead if you need to. ```json // tsconfig.json diff --git a/content/guides/references/troubleshooting.md b/content/guides/references/troubleshooting.md index 0426fbcf88..90ad180ddd 100644 --- a/content/guides/references/troubleshooting.md +++ b/content/guides/references/troubleshooting.md @@ -243,7 +243,7 @@ Cypress is built from multiple packages, each responsible for its own logging: s | `cypress:net-stubbing*` | Network interception in the proxy layer | | `cypress:server:reporter` | Problems with test reporters | | `cypress:server:preprocessor` | Processing specs | -| `cypress:server:plugins` | Running the plugin file and bundling specs | +| `cypress:server:plugins` | Running the plugins file and bundling specs | | `cypress:server:socket-e2e` | Watching spec files | | `cypress:server:task` | Invoking the `cy.task` command | | `cypress:server:socket-base` | Debugging `cy.request` command | diff --git a/content/guides/tooling/plugins-guide.md b/content/guides/tooling/plugins-guide.md index c0e9553dca..10fc867e81 100644 --- a/content/guides/tooling/plugins-guide.md +++ b/content/guides/tooling/plugins-guide.md @@ -122,13 +122,13 @@ The [Real World App (RWA)](https://github.com/cypress-io/cypress-realworld-app) -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. -⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. +⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system. diff --git a/scripts/partials.js b/scripts/partials.js index d3ab295868..bd5710ead1 100644 --- a/scripts/partials.js +++ b/scripts/partials.js @@ -18,7 +18,7 @@ module.exports.ALLOWED_TEST_CONFIG = `{% fa fa-exclamation-triangle red %} **Not module.exports.CHROMIUM_DOWNLOAD = `### Download specific Chrome version -The Chrome browser is evergreen - meaning it will automatically update itself, sometimes causing a breaking change in your automated tests. We host [chromium.cypress.io](https://chromium.cypress.io) with links to download a specific released version of Chrome (dev, Canary and stable) for every platform. +The Chrome browser is evergreen - meaning it will automatically update itself, sometimes causing a breaking change in your automated tests. We host [chromium.cypress.io](https://chromium.cypress.io) with links to download a specific released version of Chrome (dev, Canary and stable) for every platform. ` module.exports.CYPRESS_ENV_VAR_WARNING = `{% note warning "Difference between OS-level and Cypress environment variables" %} @@ -92,6 +92,6 @@ module.exports.XHR_STUBBING_DEPRECATED = [ module.exports.CODE_RUNS_IN_NODE = [ '{% note warning %}', - '⚠️ This code is part of the [plugin file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system.', + '⚠️ This code is part of the [plugins file](/guides/core-concepts/writing-and-organizing-tests.html#Plugin-files) and thus executes in the Node environment. You cannot call `Cypress` or `cy` commands in this file, but you do have the direct access to the file system and the rest of the operating system.', '{% endnote %}', ].join('\n')