From d4995a522fd2edd353055b1a8d7aaea8b45492f3 Mon Sep 17 00:00:00 2001 From: Jennifer Shehane Date: Mon, 16 Mar 2020 14:36:10 +0630 Subject: [PATCH] Remove last remaining mentions of interactive vs run mode (#2588) --- source/_changelogs/3.1.0.md | 2 +- source/_changelogs/3.8.0.md | 2 +- source/api/events/catalog-of-events.md | 4 ++-- source/guides/core-concepts/writing-and-organizing-tests.md | 2 +- source/guides/getting-started/testing-your-app.md | 2 +- source/guides/getting-started/writing-your-first-test.md | 2 +- source/guides/guides/command-line.md | 4 ++-- source/guides/guides/screenshots-and-videos.md | 4 ++-- 8 files changed, 11 insertions(+), 11 deletions(-) diff --git a/source/_changelogs/3.1.0.md b/source/_changelogs/3.1.0.md index f6df2061e5..a61c56f8da 100644 --- a/source/_changelogs/3.1.0.md +++ b/source/_changelogs/3.1.0.md @@ -29,7 +29,7 @@ - We have added support for more CI providers to automatically detect and show more relevant information in the Dashboard, instead of showing 'Unknown'. Fixes {% issue 2146 %}. - We have added better checks and reliability for detecting runs in Jenkins. Fixes {% issue 1990 %}. - The built in {% url "`cypress-browserify-preprocessor`" https://github.com/cypress-io/cypress-browserify-preprocessor %} was bumped to `1.1.0`. This supports more JavaScript features by default, including async/await, object rest spread, and class properties. Fixes {% issue 2254 %}. -- {% url "`cypress run`" command-line#cypress-run %} now creates a new browser profile per run per browser, but keeps the same browser profile for interactive mode with {% url "`cypress open`" command-line#cypress-open %}. This means you can run Cypress locally over multiple processes and the browser profiles will not conflict with each other. Fixes {% issue 1566 %}. +- {% url "`cypress run`" command-line#cypress-run %} now creates a new browser profile per run per browser, but keeps the same browser profile when run via {% url "`cypress open`" command-line#cypress-open %}. This means you can run Cypress locally over multiple processes and the browser profiles will not conflict with each other. Fixes {% issue 1566 %}. - The Desktop-GUI has been updated to get the new routes provided by the Cypress API for runs. Fixes {% issue 2189 %}. - Cypress now retries multiple times (with a backoff strategy) when communicating with our API fails while recording runs. This will provide better feedback in situations when the API is temporarily unavailable. Fixes {% issue 1590 %}. - When Cypress retries due to an API timeout or failure it now displays a very nice message indicating to you the delay and number of retries left. Fixes {% issue 2280 %}. diff --git a/source/_changelogs/3.8.0.md b/source/_changelogs/3.8.0.md index a6b7d761e2..fcf770786f 100644 --- a/source/_changelogs/3.8.0.md +++ b/source/_changelogs/3.8.0.md @@ -17,7 +17,7 @@ - We fixed a regression in {% url "3.5.0" changelog-3-5-0 %} where calling `.type({ force: true })` on hidden inputs would not type the correct characters. Fixes {% issue 5835 %}. - We fixed a regression in {% url "3.5.0" changelog-3-5-0 %} where {% url "`.type()`" type %} was not respecting previous selections if the current value of the input was the same as the key. This also fixed an where {% url "`.type()`" type %} would not respect previous selections in non-selectionRange inputs (like email or number inputs). Fixes {% issue 5703 %}. - During visibility checks, Cypress now properly evaluates a DOM element transformed by `scale(0)` or `rotateY(90deg)` as not visible. Fixes {% issue 723 %}. -- Fixed a bug where the specs list in interactive mode would not refresh when files are changed on disk. Fixes {% issue 5933 %}. +- Fixed a bug where the specs list during `cypress open` would not refresh when files are changed on disk. Fixes {% issue 5933 %}. - `env` configuration option displays properly within the settings panel. Previously, setting env options would incorrectly render `"undefined"` as the value. Fixes {% issue 5859 %}. **Misc:** diff --git a/source/api/events/catalog-of-events.md b/source/api/events/catalog-of-events.md index 57da16b79d..aa41773fc3 100644 --- a/source/api/events/catalog-of-events.md +++ b/source/api/events/catalog-of-events.md @@ -117,13 +117,13 @@ Event | Details Event | Details --- | --- **Name:** | `log:added` -**Yields:** | log attributes **(Object)**, whether Cypress is in interactive mode **(Boolean)** +**Yields:** | log attributes **(Object)**, whether Cypress is in interactive mode (running via `cypress open`) **(Boolean)** **Description:** | Fires whenever a command emits this event so it can be displayed in the Command Log. Useful to see how internal cypress commands utilize the {% url 'Cypress.log()' cypress-log %} API. Event | Details --- | --- **Name:** | `log:changed` -**Yields:** | log attributes **(Object)**, whether Cypress is in interactive mode **(Boolean)** +**Yields:** | log attributes **(Object)**, whether Cypress is in interactive mode (running via `cypress open`) **(Boolean)** **Description:** | Fires whenever a command's attributes changes. This event is debounced to prevent it from firing too quickly and too often. Useful to see how internal cypress commands utilize the {% url 'Cypress.log()' cypress-log %} API. Event | Details diff --git a/source/guides/core-concepts/writing-and-organizing-tests.md b/source/guides/core-concepts/writing-and-organizing-tests.md index 3abd3847ff..fc77dcfd24 100644 --- a/source/guides/core-concepts/writing-and-organizing-tests.md +++ b/source/guides/core-concepts/writing-and-organizing-tests.md @@ -322,7 +322,7 @@ it('can subtract numbers', function() { # Watching tests -When running in interactive mode using {% url "`cypress open`" command-line#cypress-open %} Cypress watches the filesystem for changes to your spec files. Soon after adding or updating a test Cypress will reload it and run all of the tests in that spec file. +When running in using {% url "`cypress open`" command-line#cypress-open %}, Cypress watches the filesystem for changes to your spec files. Soon after adding or updating a test Cypress will reload it and run all of the tests in that spec file. This makes for a productive development experience because you can add and edit tests as you're implementing a feature and the Cypress user interface will always reflect the results of your latest edits. diff --git a/source/guides/getting-started/testing-your-app.md b/source/guides/getting-started/testing-your-app.md index dc1c739572..d377db192b 100644 --- a/source/guides/getting-started/testing-your-app.md +++ b/source/guides/getting-started/testing-your-app.md @@ -396,5 +396,5 @@ From here you may want to explore some more of our guides: - {% url "Tutorial Videos" tutorials %} to watch step-by-step tutorial videos - {% url "Cypress API" table-of-contents %} to learn what commands are available as you work - {% url "Introduction to Cypress" introduction-to-cypress %} explains how Cypress *really* works -- {% url 'Command Line' command-line %} for running all your tests outside of interactive mode +- {% url 'Command Line' command-line %} for running all your tests outside via `cypress run` - {% url 'Continuous Integration' continuous-integration %} for running Cypress in CI diff --git a/source/guides/getting-started/writing-your-first-test.md b/source/guides/getting-started/writing-your-first-test.md index 8c88c337b8..e11cff99a1 100644 --- a/source/guides/getting-started/writing-your-first-test.md +++ b/source/guides/getting-started/writing-your-first-test.md @@ -18,7 +18,7 @@ Assuming you've successfully {% url "installed the Test Runner" installing-cypre 1. Create a `sample_spec.js` file. 2. Watch Cypress update our list of specs. -3. Launch Cypress in interactive mode. +3. Launch the Cypress Test Runner. Let's create a new file in the `cypress/integration` folder that was created for us: diff --git a/source/guides/guides/command-line.md b/source/guides/guides/command-line.md index 54aac85e62..5f8b86eebf 100644 --- a/source/guides/guides/command-line.md +++ b/source/guides/guides/command-line.md @@ -201,7 +201,7 @@ Video recording is not currently supported in Electron with the `--headed` flag. By default, Cypress will run tests in Electron headlessly. -Passing `--headed` will force Electron to be shown. This matches how you run Electron in interactive mode. +Passing `--headed` will force Electron to be shown. This matches how you run Electron via `cypress open`. ```shell cypress run --headed @@ -335,7 +335,7 @@ The Dashboard will display any tags sent with the appropriate run. ## `cypress open` -Opens the Cypress Test Runner in interactive mode. +Opens the Cypress Test Runner. ```shell cypress open [options] diff --git a/source/guides/guides/screenshots-and-videos.md b/source/guides/guides/screenshots-and-videos.md index c931b46900..448b1dd1b9 100644 --- a/source/guides/guides/screenshots-and-videos.md +++ b/source/guides/guides/screenshots-and-videos.md @@ -13,11 +13,11 @@ title: Screenshots and Videos # Screenshots -Cypress comes with the ability to take screenshots, whether you are running in interactive mode using `cypress open` or run mode using `cypress run`, even in CI. +Cypress comes with the ability to take screenshots, whether you are running via `cypress open` or `cypress run`, even in CI. To take a manual screenshot you can use the {% url `cy.screenshot()` screenshot %} command. -Additionally, Cypress will automatically capture screenshots when a failure happens during runs outside of interactive mode. +Additionally, Cypress will automatically capture screenshots when a failure happens during `cypress open`. Screenshots on failure are *not* automatically taken during `cypress open`. This behavior can be turned off by setting `screenshotOnRunFailure` to `false` in the {% url 'Cypress.Screenshot.defaults()' screenshot-api %}.