What’s New

New from the Cypress Team

• Highlight your project's test status in Github with Cypress README badges.
• Register for this Visual Component Testing webinar with Cypress and Applitools coming up on September 24th.
• Sign up for this webinar with Cypress and Curiosity Software on Model-Based testing for Cypress coming up on September 29th.

New from the Cypress Community

• Cypress Ambassador Marie Drake [@mcruzdrake] will be speaking at the upcoming Open Quality Conference about Web Accessibility and how Cypress helps bridge the gap between developers on testers. Learn more >

• Check out Filip Hric [@filip_hric] new course on Udemy, Cypress test automation for people in a hurry. There's also this post with Filip's favorite VS Code extensions for writing tests in Cypress.

Bugfixes:

Several bugs were fixed. Here are some of them (check the Changelog for the full list).

When a user exceeds the test limits of their free Cypress Dashboard plan, they’ll now see a warning message in the stdout.

You can now specify retries as a TestOptions type.

Types for specType field on Cypress.spec have been added.

There was a typo in the Typescript definitions where it said TestCptions rather than TestOptions (whoops) and now this has been fixed.

It was possible to run a never ending test accidentally when nesting hooks within other hooks and so now that has been fixed.

Cypress now resolves and loads tsconfig.json for TypeScript projects starting from the plugins directory.

There was an issue where, if npm config’s noproxy was set, unexpected behavior could occur. That has now been fixed.

There was an issue where test would unexpectedly fail with a “can’t resolve ‘async_hooks’” error. That has now been fixed.

There was an issue where return values from blob utils were mistaken for promises and could cause errors. That has now been fixed.

Now, cy.trigger() includes the view property in the event object when that is appropriate.

Bug Fixes and Improvements

If you’ve ever seen the error Cannot set property 'err' of undefined incorrectly when rerunning tests in the Test Runner, you won’t anymore because it is fixed. 

If you’ve ever seen the Cannot read property ‘isAttached’ of undefined error during cypress run on Firefox versions >= 75, you won’t anymore because it is fixed.

If you’ve ever seen the error Maximum call stack size exceeded when calling scrollIntoView on an element in the shadow dom you won’t anymore because it is fixed.

Cypress environment variables that accept arrays as their value will now properly evaluate as arrays. 

Elements that have display: inline will no longer be considered hidden if they have child elements within them that are visible.

If a test fails in an afterEach or beforeEach hook after the hook has already passed, screenshots will now be correctly taken.

Speaking of screenshots, Cypress will no longer report screenshots overwritten in a cy.screenshot() onAfterScreenshot option as a unique screenshot. 

Additionally, taking screenshots will no longer fail when the screenshot names are too long for the filesystem to accept. Go ahead, go crazy with those screenshot names. 

Now Cypress will correctly remember the “last used browser” during cypress open if a non-default-channel browser was selected.

reporterStats will now correctly show the number of passed and failed tests when a test passes but the afterEach fails. 

The Developer Tools menu will now always display in Electron when switching focus from Specs to the Test Runner.

Check the Changelog for the complete release notes.

New from the Cypress Team

• When Can the Test Navigate - Learn how to change a deceptively simple test into a reliable and flake free one. 
• Watch our recent webcast about how GoFundMe’s QA engineers and developers test 30x faster with Cypress.

New from the Cypress Community

• [@mcruzdrake] Debunking Accessibility Testing Myths
• [@md_zubairahmed] Modern ways of end-to-end testing with Cypress JS
• [@wescopeland] Cypress super patterns: How to elevate the quality of your test suite

Test Analytics for the Cypress Dashboard is a huge step forward in our mission to help teams easily manage and improve their test suites, so developers can build better things with confidence.

With today’s release of Test Analytics, Cypress Dashboard users will notice four major new features: top failures, slowest tests, test case history, and project analytics like run status, run duration and more. 

Dashboard users can now find the troublemakers in their test suite, manage issues with ease, and unlock a deeper, unprecedented understanding of their tests. Read more>

Not using Cypress Dashboard yet? The Cypress Dashboard adds a layer of timely, simple and powerful insights to all your test runs in a single, easy-to-use Dashboard. Test and debug faster with The Cypress Dashboard. Get started for free.

• Bug fixes and improvements

  • position: fixed elements that have a parent with pointer-events: none will now correctly evaluate as visible. 
  • Applications using custom elements will no longer trigger infinite XHR request loops. 
  • When snapshotting the DOM, Cypress no longer causes attributeChangedCallback to be triggered on custom elements.
  • Spec files containing + characters now properly run in Cypress. 
  • When using the fx shortcut in cy.route(), an error is now thrown when the fixture file cannot be found. 
  • Cypress no longer thrown Cannot read property '__error' of null error when passing a file containing null content to cy.fixture(). 
  • Values containing exponential operators passed to --env via the command line are now properly read. 
  • The “Open in IDE” button no longer disappears from hooks when the tests are manually rerun. 
  • When experimentalSourceRewriting is enabled, AST rewriting will no longer return an output before the body is done being written. This would happen when the response body was too large and the response would be sent while the body was still being modified. 
  • When using .type(), Cypress now properly types into an input within an iframe that auto focuses the input.

• Setting viewportHeight or viewportWidth from within the test configuration now properly changes the viewport size for the duration of the suite or test.
• Setting deep objects and arrays on config within the pluginsFile now sets the values correctly. Fixes #7959.
• The progress bar for cy.wait() now reflects the correct requestTimeout and responseTimeout of the command. Fixes #7881.
• The command’s progress bar will not longer restart when its parent test is collapsed in the Command Log. Fixes #7912.
• Key value pairs sent to ELECTRON_EXTRA_LAUNCH_ARGS as key=value will now be properly read in. Fixes #7994.
• Stubbed responses responding with an empty string to cy.route() now correctly display as ‘xhr stub’ in the Test Runner’s Command Log. Fixes #8018.
• Quickly reclicking the “Run All Tests” button in the Test Runners’ Command Log will no longer throw errors about undefined properties and the tests will no longer hang. Fixes #7968.

Bug fixes and improvements

• We (specifically the Cypress proxy layer) will no longer prematurely cancel HTTP requests taking longer than the default responseTimeout.
• Using Cypress commands to traverse the DOM on an application with a global parent variable will no longer throw Illegal Invocation errors. 
• When experimentalShadowDomSupport is enabled, using .type() on an input in the Shadow DOM will not result in an error. 
• When experimentalShadowDomSupport is enabled, checking for visibility on a shadow dom host element will no longer hang if the host element was the foremost element and had an ancestor with fixed position. 
• Debug logs from the @benmalka/foxdriver module will no longer appear if any DEBUG environment variable was set. 
• We made a few minor UI updates to the Test Runner.
• Update to 4.10.0 with npm install --save-dev [email protected]

New from the Cypress Community

• [@tlakomy] Add e2e tests with Cypress to a React application
• [@mcruzdrake] API testing with Cypress

Our new Slack app is live! Now, when you connect your Cypress organization with your Slack instance in the Cypress Dashboard, you’ll see run results for all projects in your org posted to the Slack channel of your choice. 

Not sure what the Cypress Dashboard is? The Cypress Dashboard is available to anyone running tests with Cypress. It adds a layer of timely, simple and powerful insights to all your test runs in a single, easy-to-use Dashboard. Test and debug faster with The Cypress Dashboard. Get started for free.