Bump cypress from 6.9.1 to 7.1.0

[dependabot]

Bumps cypress from 6.9.1 to 7.1.0.

Release notes

Sourced from cypress's releases.

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.

Bugfixes:

• Viewport configuration set in cypress.json is now correctly applied in the Component Test Runner. Fixes #15899.
• Running specs on Windows is now supported in the Component Test Runner. Fixes #15842.
• Fixed an issue where crashes in Cypress would cause a misleading "Unknown signal: true" error after the actual crash message. Fixes #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.

7.0.1

Released 04/07/2021

Bugfixes:

• Fixed a regression in 7.0.0 that caused the test runner not to check for updates. Fixes #15829.
• The component testing spec list search input no longer throws an exception when hitting Enter. Addressed in #15833.
• The preferred file opener modal no longer appears behind the command log. Addressed in #15831.
• Cypress no longer crashes in certain circumstances when running in Docker without --ipc=host. Fixes #15814 and #350.
• Node.js warnings are no longer incorrectly printed to stderr in production builds of Cypress. Addressed in #15817.
• Cypress no longer prints a warning to stdout when the video cannot be found after a run. Addressed in #15828.
• A warning is no longer displayed when running a TypeScript spec without a tsconfig.json file present. Addressed in #15828.

Misc:

• The "New Spec File" in the Desktop GUI has a less pronounced style. Addressed in #15835.

7.0.0

Released 04/05/2021

Summary:

🎉 Introducing the Cypress Component Test Runner - now in alpha. Today's release includes a brand new test runner designed to replace your Node-based component tests. Our Component Test Runner tests your components in the browser, just like a user would. And, since it runs in the browser, you get to debug your components using your favorite developer tools. Read our Component Testing Guide for more details.

Breaking Changes:

Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 7.0.

• We introduced several breaking changes to cy.intercept(). See the https://github.com/cypress-io/cypress/blob/HEAD[https://github.com/cypress-io/cypress/blob/HEADchttps://github.com/cypress-io/cypress/blob/HEADyhttps://github.com/cypress-io/cypress/blob/HEAD.https://github.com/cypress-io/cypress/blob/HEADihttps://github.com/cypress-io/cypress/blob/HEADnhttps://github.com/cypress-io/cypress/blob/HEADthttps://github.com/cypress-io/cypress/blob/HEADehttps://github.com/cypress-io/cypress/blob/HEADrhttps://github.com/cypress-io/cypress/blob/HEADchttps://github.com/cypress-io/cypress/blob/HEADehttps://github.com/cypress-io/cypress/blob/HEADphttps://github.com/cypress-io/cypress/blob/HEADthttps://github.com/cypress-io/cypress/blob/HEAD(https://github.com/cypress-io/cypress/blob/HEAD)https://github.com/cypress-io/cypress/blob/HEAD]https://github.com/cypress-io/cypress/blob/HEAD(https://github.com/cypress-io/cypress/blob/HEAD/https://github.com/cypress-io/cypress/blob/HEADahttps://github.com/cypress-io/cypress/blob/HEADphttps://github.com/cypress-io/cypress/blob/HEADihttps://github.com/cypress-io/cypress/blob/HEAD/https://github.com/cypress-io/cypress/blob/HEADchttps://github.com/cypress-io/cypress/blob/HEADohttps://github.com/cypress-io/cypress/blob/HEADmhttps://github.com/cypress-io/cypress/blob/HEADmhttps://github.com/cypress-io/cypress/blob/HEADahttps://github.com/cypress-io/cypress/blob/HEADnhttps://github.com/cypress-io/cypress/blob/HEADdhttps://github.com/cypress-io/cypress/blob/HEADshttps://github.com/cypress-io/cypress/blob/HEAD/https://github.com/cypress-io/cypress/blob/HEADihttps://github.com/cypress-io/cypress/blob/HEADnhttps://github.com/cypress-io/cypress/blob/HEADthttps://github.com/cypress-io/cypress/blob/HEADehttps://github.com/cypress-io/cypress/blob/HEADrhttps://github.com/cypress-io/cypress/blob/HEADchttps://github.com/cypress-io/cypress/blob/HEADehttps://github.com/cypress-io/cypress/blob/HEADphttps://github.com/cypress-io/cypress/blob/HEADthttps://github.com/cypress-io/cypress/blob/HEAD)https://github.com/cypress-io/cypress/blob/HEAD docs for full usage examples. Breaking changes:
  • Request handlers supplied to cy.intercept() are now matched starting with the most recently defined request interceptor. This allows users to override request handlers by calling cy.intercept() again. This matches the previous behavior that was default in cy.route(). Addresses #9302.
  • cy.intercept() now automatically parses more JSON MIME types, including 'application/vnd.api+json'. You can now remove JSON.parse(req.body) or JSON.parse(res.body) from some tests that previously required it. Addresses #14763.
  • Falsy values (with the exception of undefined) supplied as the body of a StaticResponse to cy.intercept() will now be JSONified and sent as the body. Previously, an empty string was sent instead. Addresses #15234 and #14205.
  • The matchUrlAgainstPath RouteMatcher property has been removed from cy.intercept().
  • The "substring match" from cy.intercept() URL matching has been removed. Previously, a URL would match if it contained the supplied string anywhere. Now, the URL (including querystring) only matches if it is an equality match or a minimatch.
  • The delay option for StaticResponses used with cy.intercept() has been removed. Please go back to using the delayMS option. Addresses #15255.
  • cy.route2() was previously aliased to cy.intercept(). Now the alias cy.route2() has been removed. Please update usage of cy.route2() to cy.intercept(). Addressed in #14709.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)