Merge branch 'v12' into content/update-session-api-docs

Author: emilyrohrbough

content/_changelogs/12.0.0.md

@@ -0,0 +1,13 @@
+## 11.0.0
+
+_Released MM/DD/YYYY_
+
+**Breaking Changes:**
+
+- `experimentalSessionAndOrigin` flag has been removed and all functionality is
+  on by default now.
+- `testIsolation` defaults to `strict` now.
+- `Cookies.defaults` and `Cookies.preserveOnce` have been removed. Please update
+  to use [`cy.session()`](/api/commands/session) to preserve session details
+  between tests. Addresses
+  [#21472](https://github.com/cypress-io/cypress/issues/21472).

content/_data/sidebar.json

@@ -320,10 +320,6 @@
             {
               "title": "Cross Browser Testing",
               "slug": "cross-browser-testing"
-            },
-            {
-              "title": "Web Security",
-              "slug": "web-security"
             }
           ]
         },
@@ -727,10 +723,6 @@
               "title": "root",
               "slug": "root"
             },
-            {
-              "title": "route",
-              "slug": "route"
-            },
             {
               "title": "screenshot",
               "slug": "screenshot"
@@ -751,10 +743,6 @@
               "title": "selectFile",
               "slug": "selectfile"
             },
-            {
-              "title": "server",
-              "slug": "server"
-            },
             {
               "title": "session",
               "slug": "session"
@@ -911,10 +899,6 @@
               "title": "SelectorPlayground",
               "slug": "selector-playground-api"
             },
-            {
-              "title": "Server",
-              "slug": "cypress-server"
-            },
             {
               "title": "arch",
               "slug": "arch"

content/api/commands/intercept.md

@@ -11,13 +11,6 @@ Spy and stub network requests and responses.
 
 </Alert>
 
-<Alert type="bolt">
-
-`cy.intercept()` is the successor to `cy.route()` as of Cypress 6.0.0. See
-[Comparison to `cy.route`](#Comparison-to-cy-route).
-
-</Alert>
-
 <Alert type="warning">
 
 All intercepts are automatically cleared before every test.
@@ -1486,16 +1479,6 @@ Cypress.minimatch('http://localhost/users?_limit=3', '**/users?_limit=+(3|5)', {
 // true (plus debug messages)
 ```
 
-## Comparison to `cy.route()`
-
-Unlike [cy.route()](/api/commands/route), `cy.intercept()`:
-
-- can intercept all types of network requests including Fetch API, page loads,
-  XMLHttpRequests, resource loads, etc.
-- does not require calling [cy.server()](/api/commands/server) before use - in
-  fact, `cy.server()` does not influence `cy.intercept()` at all.
-- does not have method set to `GET` by default, but intercepts `*` methods.
-
 ## `cy.intercept()` and request caching
 
 `cy.intercept()` intercepts requests at the network layer. This can cause
@@ -1597,7 +1580,6 @@ information about the request and response to the console:
 - [Network Requests Guide](/guides/guides/network-requests)
 - [Cypress Example Recipes](https://github.com/cypress-io/cypress-example-recipes#stubbing-and-spying)
 - [Kitchen Sink Examples](https://github.com/cypress-io/cypress-example-kitchensink/blob/master/cypress/integration/2-advanced-examples/network_requests.spec.js)
-- [Migrating `cy.route()` to `cy.intercept()`](/guides/references/migration-guide#Migrating-cy-route-to-cy-intercept)
 <!-- TODO add examples from the resources below to `cypress-example-recipes` repo -->
 - [Smart GraphQL Stubbing in Cypress](https://glebbahmutov.com/blog/smart-graphql-stubbing/)
   blog post

content/api/commands/origin.md

@@ -13,36 +13,6 @@ limitation determined by standard web security features of the browser. The
 
 <Alert type="warning">
 
-<strong class="alert-header"><Icon name="exclamation-triangle"></Icon>
-Experimental</strong>
-
-The `session` API is currently experimental, and can be enabled by setting the
-[`experimentalSessionAndOrigin`](/guides/references/experiments) option to
-`true` in the Cypress config.
-
-Enabling this flag does the following:
-
-- It adds the `cy.session()` and [`cy.origin()`](/api/commands/origin) commands,
-  and [`Cypress.session`](/api/cypress-api/session) API.
-- It adds the concept of
-  [`testIsolation`](/guides/core-concepts/writing-and-organizing-tests#Test-Isolation)
-  which defaults to `on`, such that:
-  - The page is cleared (by setting it to `about:blank`).
-  - Cookies, local storage and session storage in all domains are cleared.
-- It supersedes the
-  [`Cypress.Cookies.preserveOnce()`](/api/cypress-api/cookies#Preserve-Once) and
-  [`Cypress.Cookies.defaults()`](/api/cypress-api/cookies#Defaults) methods.
-- Cross-origin requests will now succeed, however, to interact with a
-  cross-origin page you must use a `cy.origin` block.
-
-Because the page is cleared at the beginning of each test by default,
-[`cy.visit()`](/api/commands/visit) must be explicitly called at the beginning
-of each test.
-
-</Alert>
-
-<Alert type="warning">
-
 <strong class="alert-header"><Icon name="exclamation-triangle"></Icon>
 Obstructive Third Party Code</strong>
 
@@ -340,9 +310,8 @@ performant. Up until now you could get around this problem by putting login code
 in the first test of your file, then performing subsequent tests reusing the
 same session.
 
-However, once the `experimentalSessionAndOrigin` flag is activated, this is no
-longer possible, since all session state is now cleared between tests. So to
-avoid this overhead we recommend you leverage the
+However, this is no longer possible, since all session state is now cleared
+between tests. So to avoid this overhead we recommend you leverage the
 [`cy.session()`](/api/commands/session) command, which allows you to easily
 cache session information and reuse it across tests. So now let's enhance our
 custom login command with `cy.session()` for a complete syndicated login flow
@@ -385,81 +354,6 @@ and reuse it across tests.
 
 ## Notes
 
-### Migrating existing tests
-
-Enabling the `experimentalSessionAndOrigin` flag makes the test-runner work
-slightly differently, and some test suites that rely on the existing behaviour
-may have to be updated. The most important of these changes is
-[**test isolation**]() which defaults to `on`. This means that after every test,
-the current page is reset to `about:blank` and cookies, local storage and
-session storage in all domains are cleared before each test. This change is
-opt-in for now, but will be standardized in a future major release of Cypress,
-so eventually all tests will need to be isolated.
-
-Before this change, it was possible to write tests such that you could, for
-example, log in to a CMS in the first test, change some content in the second
-test, verify the new version is displayed on a different URL in the third, and
-log out in the fourth. Here's a simplified example of such a test strategy.
-
-<Badge type="danger">Before</Badge> Multiple small tests against different
-origins
-
-```js
-it('logs in', () => {
-  cy.visit('https://supersecurelogons.com')
-  cy.get('input#password').type('Password123!')
-  cy.get('button#submit').click()
-})
-
-it('updates the content', () => {
-  cy.get('#current-user').contains('logged in')
-  cy.get('button#edit-1').click()
-  cy.get('input#title').type('Updated title')
-  cy.get('button#submit').click()
-  cy.get('.toast').type('Changes saved!')
-})
-
-it('validates the change', () => {
-  cy.visit('/items/1')
-  cy.get('h1').contains('Updated title')
-})
-```
-
-After switching on `experimentalSessionAndOrigin`, this flow would need to be
-contained within a single test. While this practice has always been
-[discouraged](/guides/references/best-practices#Having-tests-rely-on-the-state-of-previous-tests)
-we know some users have historically written tests this way, often to get around
-the same-origin restrictions. But with `cy.origin()` you no longer need these
-kind of brittle hacks, as your multi-origin logic can all reside in a single
-test, like the following.
-
-<Badge type="success">After</Badge> One big test using `cy.origin()`
-
-```js
-it('securely edits content', () => {
-  cy.origin('supersecurelogons.com', () => {
-    cy.visit('https://supersecurelogons.com')
-    cy.get('input#password').type('Password123!')
-    cy.get('button#submit').click()
-  })
-
-  cy.origin('mycms.com', () => {
-    cy.url().should('contain', 'cms')
-    cy.get('#current-user').contains('logged in')
-    cy.get('button#edit-1').click()
-    cy.get('input#title').type('Updated title')
-    cy.get('button#submit').click()
-    cy.get('.toast').type('Changes saved!')
-  })
-
-  cy.visit('/items/1')
-  cy.get('h1').contains('Updated title')
-})
-```
-
-Always remember,
-[Cypress tests are not unit tests](https://docs.cypress.io/guides/references/best-practices#Creating-tiny-tests-with-a-single-assertion).
-
 ### Serialization
 
 When entering a `cy.origin()` block, Cypress injects itself at runtime, with all
@@ -642,9 +536,6 @@ following Cypress commands will throw errors if used in the callback:
 - `cy.origin()`
 - [`cy.intercept()`](/api/commands/intercept)
 - [`cy.session()`](/api/commands/session)
-- [`cy.server()`](/api/commands/server)
-- [`cy.route()`](/api/commands/route)
-- [`Cypress.Cookies.preserveOnce()`](/api/cypress-api/cookies)
 
 ### Other limitations
 

content/api/commands/request.md

@@ -357,12 +357,9 @@ browser cookies.
 In other words, `cy.request()` transparently performs all of the underlying
 functions as if it came from the browser.
 
-### [`cy.intercept()`](/api/commands/intercept), [`cy.server()`](/api/commands/server), and [`cy.route()`](/api/commands/route)
+### [`cy.intercept()`](/api/commands/intercept)
 
-#### `cy.request()` sends requests to actual endpoints, bypassing those defined using `cy.route()` or `cy.intercept()`
-
-`cy.server()` and any configuration passed to
-[`cy.server()`](/api/commands/server) has no effect on `cy.request()`.
+#### `cy.request()` sends requests to actual endpoints, bypassing those defined using `cy.intercept()`
 
 The intention of `cy.request()` is to be used for checking endpoints on an
 actual, running server without having to start the front end application.