build(deps-dev): bump cypress from 4.2.0 to 5.1.0
Created by: Tirokk
Authored by dependabot-preview[bot] Closed
Bumps cypress from 4.2.0 to 5.1.0.
Release notes
Sourced from cypress's releases.
5.1.0
Released 9/1/2020
Features:
- Introducing experimental full network stubbing support
🎉 .
- With
experimentalNetworkStubbing
enabled, thecy.route2
command is available.- By using cy.route2(), your tests can intercept, modify, and wait on any type of HTTP request originating from your app, including
XMLHttpRequest
s,fetch
requests, beacons, and subresources (like iframes and scripts).- Outgoing HTTP requests can be modified before reaching the destination server, and the HTTP response can be intercepted as well before it reaches the browser.
- See the cy.route2() docs for more information on how to enable this experiment.
cy.trigger()
now accepts aneventConstructor
option for specifying the constructor with which to create the event to trigger. Addresses #5650.Bugfixes:
- Improved warnings for when user is exceeding test limits of the free Dashboard plan. Addresses #8409.
- Added
retries
toTestOptions
types. Addresses #8405.- Added types for
specType
field onCypress.spec
. Addresses #8256.- Fixed a typo in type definitions. Addresses #8417.
- Cypress now resolves and loads tsconfig.json for TypeScript projects starting from the plugins directory. Addresses #8359.
- Fixed an issue where, if npm config's
noproxy
is set, unexpected behavior could occur. Addresses #8287.- Fixed an issue where nesting hooks within other hooks caused the test to never finish. Addresses #8350.
- Fixed an issue in where tests would unexpectedly fail with a "Can't resolve 'async_hooks'" error. Addresses #8375.
- Fixed an issue where return values from blob utils were mistaken for promises and could cause errors. Addresses #8365.
- Fixed an issue with loading
.mjs
files. Addresses #8361.- Fixed an issue causing tests to run slowly in Electron. Addresses #7930.
- Using
.should
with only chainer assertions will now throw an error. Addresses #883.cy.trigger()
now includes theview
property in the event object when appropriate. Addresses #3686.- Fixed an issue where Cypress would not detect newer 64-bit installations of Chrome on Windows. Addresses #8425.
- Fixed an issue where Cypress would not detect per-user Firefox installations on Windows. Addresses #8432.
Dependency Updates:
- Updated dependency
iconv-lite
to version0.6.2
. Addresses #8387.- Updated dependency
command-exists
to version1.2.9
. Addresses #8388.- Updated dependency
electron
to version9.2.1
. Addresses #8436.5.0.0
Released 8/19/2020
Summary:
Cypress now includes support for test retries! Similar to how Cypress will retry assertions when they fail, test retries will allow you to automatically retry a failed test prior to marking it as failed. Read our new guide on Test Retries 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 5.0.
- The
cypress-plugin-retries
plugin has been deprecated in favor of test retries built into Cypress. Addresses #1313.- The
Cypress.Cookies.defaults()
whitelist
option has been renamed topreserve
to more closely reflect its behavior. Addressed in #7782.- The
blacklistHosts
configuration has been renamed toblockHosts
to more closely reflect its behavior. Addressed in #7622.
Commits
-
36bc52e
release 5.1.0 [skip ci] -
ad8822d
fix(launcher): detect Firefox installed in AppData on Windows (#8460) -
1ad9bd1
fix: error when spec code registers nested hooks (#8400) -
c0ab5c8
chore: fix typo (#8452) -
15fdf12
feat: can dispatch events with the type they want. (#8305) -
2469473
chore: rename experimental network stubbing (#8450) -
b448c16
fix(launcher): detect new Chrome 64-bit path on Windows (#8449) -
c378960
feat(net-stubbing): experimental full network mocking support (#4176) -
cc5aafc
fix: don't scaffold integration when using component tests (#8315) -
032b869
chore(deps): update dependency electron to version 9.2.1🌟 (#8436) - Additional commits viewable 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) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language -
@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)