build(deps-dev): bump cypress from 3.6.1 to 3.7.0

Created by: Tirokk

Authored by dependabot-preview[bot] Nov 28, 2019 Merged Nov 28, 2019

---

Bumps cypress from 3.6.1 to 3.7.0.

Release notes

Sourced from cypress's releases.

3.7.0

Released 11/27/2019

Features:

• Cypress now includes the full list of browsers found and their properties within the Cypress configuration. This means that the browsers array is also editable within plugins by accessing config.browsers via the Configuration API. The currently available browsers are also displayed within the configuration panel under Settings in the Test Runner. Addresses #5067.
• Environment variables within GitHub Actions are now detected and passed to the Dashboard in order to display the proper git information for recorded runs. Fixes #5609.

Bugfixes:

• Fixed a regression in 3.5.0 where a cy.visit that changes superdomain would incorrectly clear cookies of other domains. Fixes #5756.
• Fixed a regression in 3.5.0 where cookies set in a redirect on a cy.visit or in a cy.request with a custom Domain that is not a subdomain of the current domain would fail to set. Fixes #5656.
• Fixed a regression introduced in 3.5.0 which caused cy.type to send duplicate modifier keys. Fixes #5622.
• We fixed a regression in 3.6.1 where cy.request() with followRedirect: false would fail if a Set-Cookie header was present in the response. Fixes #5654.
• The context of window is no longer undefined within the application under test when called within a setTimeout during strict mode. Fixes #5707.
• Cypress now captures the SHA of builds generated through Travis CI during pull requests. This should resolve issues with Cypress status checks sometimes not running within GitHub Integration. Fixes #5728.
• Cypress now automatically strips double quotes from --ci-build-id and group flag arguments during cypress run. Fixes #5686.
• Assertions printed in the Command Log now correctly identify integers from string integers. Fixes #25.
• Empty spaces are now accurately reflected in the Command Log within assertions. Fixes #1360.
• Keys printed in the Command Log when using the have.all.keys assertion now correctly display. Fixes #753.
• We fixed an issue where Cypress would throw an error when using cy.visit() on a cleverapp.io domain. Fixes #5722.
• Fixed a bug where fixtures consisting only of null would cause an error. Fixes #472.
• Fixed a bug where, if the Test Runner child process is killed with a signal and does not exit normally, the npm CLI process would not exit with an error. Fixes #5808.

Misc:

• Added a new, more specific error message when an item is not visible because it has position: fixed and is being overflowed over. Addresses #1379.
• cy.visits that cause a superdomain change will now result in 2 requests to the origin server. This should not affect tests, as tests will still re-run on a superdomain change. This is a side-effect of the fix for #5756.
• The configuration object returned from the plugins file is now validated and will throw a helpful error message when invalid. Addresses #5712.
• The configuration panel under Settings in the Test Runner now has a white background for better readability. Also each configuration option with nested properties is now collapsible. Addressed in #5068.

Dependency Updates:

• Upgraded parse-domain from 2.0.0 to 2.3.4. Addressed in #5726.

Commits

• b96071b release 3.7.0 [skip ci]
• 5e3b4bd Revert "fix type when previous selection in input in some cases" (#5812)
• 0ddedfa Revert "fix type when previous selection in input in some cases (#5809)"
• bfb9d83 fix type when previous selection in input in some cases (#5809)
• 64f5bf0 catch child process killed with a signal (#5810)
• 0311c58 TypeScriptify reporter. (#5666)
• e19bcc0 CI should fail when something went wrong. (#5779)
• e313f8c Fixed reporter unit-test failures. (#5775)
• 26ed04b Fixed null JSON file error. (#5562)
• 421bed6 Enable e2e test run on windows systems (#5586)
• 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)