Improve this doc

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.

Option Default Description
experimentalComponentTesting false Enables component testing using framework-specific adaptors. See Component Testing for more detail.
experimentalFetchPolyfill false 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.
experimentalRunEvents false Allows listening to the before:run, after:run, before:spec, and after:spec events in the plugins file.
experimentalSourceRewriting false Enables AST-based JS/HTML rewriting. This may fix issues caused by the existing regex-based JS/HTML replacement algorithm. See #5273 for details.


Version Changes
6.0.0 Removed experimentalNetworkStubbing and made it the default behavior when using cy.intercept().
6.0.0 Deprecated experimentalFetchPolyfill.
5.2.0 Removed experimentalShadowDomSupport and made it the default behavior.
5.1.0 Added support for experimentalNetworkStubbing.
5.0.0 Removed experimentalGetCookiesSameSite and made it the default behavior.
4.9.0 Added support for experimentalFetchPolyfill.
4.8.0 Added support for experimentalShadowDomSupport.
4.6.0 Added support for experimentalSourceRewriting.
4.5.0 Added support for experimentalComponentTesting.
4.3.0 Added support for experimentalGetCookiesSameSite.