If you'd like to try out what we're working on in the Test Runner, you can enable beta features for your project by turning on the experimental features you'd like to try.
⚠️ The experimental features might change or ultimately be removed without making it into the core product. Our primary goal for experiments is to collect real-world feedback during their development.
You can pass the configuration options below to enable or disable experiments. See our Configuration Guide on how to pass configuration to Cypress.
|Automatically replaces |
window.fetch with a polyfill that Cypress can spy on and stub. Note:
experimentalFetchPolyfill has been deprecated in Cypress 6.0.0 and will be removed in a future release. Consider using cy.intercept() to intercept
fetch requests instead.
|Allows listening to the |
after:spec events in the plugins file during interactive mode.
|Enables AST-based JS/HTML rewriting. This may fix issues caused by the existing regex-based JS/HTML replacement algorithm. See #5273 for details.|
|Generate and save commands directly to your test suite by interacting with your app as an end user would. See Cypress Studio for more details.|
|7.1.0||Added support for |
experimentalComponentTesting and made it the default behavior.
experimentalRunEvents and made it the default behavior.
|6.3.0||Added support for |
|6.2.0||Added support for |
experimentalNetworkStubbing and made it the default behavior when using cy.intercept().
experimentalShadowDomSupport and made it the default behavior.
|5.1.0||Added support for |
experimentalGetCookiesSameSite and made it the default behavior.
|4.9.0||Added support for |
|4.8.0||Added support for |
|4.6.0||Added support for |
|4.5.0||Added support for |
|4.3.0||Added support for |