@cypress/schematic
6.0.0 · 26 Aug 2026MIT116k / weekRepositoryHomepagenpmAtom feed
38 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 6.x · latest line
6.0.0
26 Aug 2026- Deprecated
cy.server()andcy.route()have been deprecated. In a future release, support forcy.server()andcy.route()will be moved to a plugin. We encourage you to usecy.intercept()instead. Addressed in #9185. - Deprecated
experimentalFetchPolyfillhas been deprecated. We encourage you to usecy.intercept()to intercept requests using the Fetch API instead. Cypress now always throws an error when asserting on an element that doesn't exist in the DOM (unless you're asserting that the element should
not.exist). Assertions such asnot.visible,not.contains,not.have.class, etc will now fail when used on non-existent DOM elements. Addresses #205.
Released 11/23/2020
Summary:
Cypress now offers full network stubbing support with the introduction of the
cy.intercept()command (previouslycy.route2()). Withcy.intercept()your tests can intercept, modify and wait on any type of HTTP request originating from your app.Breaking Changes:
Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 6.0.
Cypress now always throws an error when asserting on an element that doesn't exist in the DOM (unless you're asserting that the element should
not.exist). Assertions such asnot.visible,not.contains,not.have.class, etc will now fail when used on non-existent DOM elements. Addresses #205.DOM elements where the CSS style (or ancestors) are
opacity: 0are no longer considered visible. However these are still considered actionable and "any action commands" interacting-with-elements#Actionability used to interact with the element will perform the action. This matches browser's implementation on how they regard elements withopacity: 0. Addresses #4474.The type yielded by
cy.wait(alias)has changed in order to support use ofcy.intercept(). Addressed in #9266.The
experimentalNetworkStubbingoption has been removed and made the default behavior. You can safely removed this configuration option. Addressed in #9185.When using
.type()and.click()on elements inside acontenteditableelement, the events are now properly triggered on the inside elements. This may cause unintended consequences if you were relying on the previous behavior. Addressed in #9066.We removed several deprecation errors around APIs that were removed in versions of Cypress prior to 4.0.0. This will not cause any changes for anyone upgrading from a 4.0+ version of Cypress. For a full list of all APIs affected see #8946.
We updated our HTTP status codes and reason phrases to match Node.js
http.STATUS_CODES. If you have code that relies on a reason phrase, then this could affect you. Addressed in #8969.JSON request and response bodies captured by
cy.intercept()are now automatically parsed, removing the need to manually doJSON.parse. Addressed in #9280.
Deprecations:
Deprecations still work as before but will be removed from Cypress in a future release. We encourage you to update your code now to remove uses of deprecations.
- Deprecated
cy.server()andcy.route()have been deprecated. In a future release, support forcy.server()andcy.route()will be moved to a plugin. We encourage you to usecy.intercept()instead. Addressed in #9185. - Deprecated
experimentalFetchPolyfillhas been deprecated. We encourage you to usecy.intercept()to intercept requests using the Fetch API instead. cy.route2()was renamed tocy.intercept(). We encourage you to update usages ofcy.route2()to usecy.intercept(). Addressed in #9182.
Features:
The new
cy.intercept()command can be used to manage the behavior of HTTP requests at the network layer. Addressed in #9182.We now pass
—disable-dev-shm-usageto the Chrome browser flags by default. This will write shared memory files into/tmpinstead of/dev/shm. If you're passing this flag in yourpluginsfile, you can now remove this code. Addresses #5336.A warning is now displayed when passing invalid configuration keys through the CLI. Addresses #428.
The
cypress versioncommand now also displays the current Electron and bundled Node versions. Addresses #9180.The
cypress versioncommand now accepts a--componentflag that allows you to print the version of specific components of Cypress. ie Electron, Node, etc. Addresses #9214.
Bugfixes:
We fixed a regression introduced in 3.5.0 that would cause
.type()to not type the entire string when focus was called away from the target element. Fixes #9254..type()and.click()now properly work on elements inside acontenteditableelement. Fixes #2717 and #7721.We fixed a regression introduced in 5.6.0 that would cause the Test Runner to crashes and display a white page when switching tabs while tests are running. Fixes #9151.
Fixed an issue where
Content-Lengthforcy.route2request bodies could be incorrectly recalculated. Fixes #9166.
Documentation Changes:
Our Migration Guide has a new section for 6.0 migration.
Many of our docs examples have been updated to use
cy.intercept()in place ofcy.route()including our Network Requests doc.
Misc:
Added the type of
redirectsand changedredirectedToUrloptional for Response types. Addresses #9275.
Dependency Updates
- 5.x
5.0.0
19 Dec 2025- Deprecated
The
cypress-plugin-retriesplugin has been deprecated in favor of test retries built into Cypress. Addresses #1313. - Breaking
Cypress no longer supports file paths with a question mark
?in them. We now use the webpack preprocessor by default and it does not support files with question marks. Addressed in #7982. - Breaking
Cypress now requires TypeScript 3.4+. Addressed in #7856.
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.
- Deprecated
The
cypress-plugin-retriesplugin has been deprecated in favor of test retries built into Cypress. Addresses #1313. The
Cypress.Cookies.defaults()whitelistoption has been renamed topreserveto more closely reflect its behavior. Addressed in #7782.The
blacklistHostsconfiguration has been renamed toblockHoststo more closely reflect its behavior. Addressed in #7622.The
cy.server()whitelistoption has been renamed toignoreto more closely reflect its behavior. Addresses #6642.libgbm-devis now a requirement to run Cypress on Linux. Addressed in #7791.Values yielded by
cy.setCookie(),cy.getCookie(), andcy.getCookies()will now contain thesameSiteproperty if specified. Addresses #6892.The
experimentalGetCookiesSameSiteconfiguration flag has been removed, since this behavior is now the default. Addresses #6892.The return type of the
Cypress.BlobmethodsarrayBufferToBlob,base64StringToBlob,binaryStringToBlob, anddataURLToBlobhave changed fromPromise<Blob>toBlob. Addresses #6001.- Breaking
Cypress no longer supports file paths with a question mark
?in them. We now use the webpack preprocessor by default and it does not support files with question marks. Addressed in #7982. For TypeScript compilation of spec, support, and plugins files, the
esModuleInteropoption is no longer coerced totrue. If you need to utilizeesModuleInterop, set it in yourtsconfig.json. Addresses #7575.- Breaking
Cypress now requires TypeScript 3.4+. Addressed in #7856.
- Breaking
Installing Cypress on your system now requires Node.js 10+. Addresses #6574.
In spec files, the values for the globals
__dirnameand__filenameno longer include leading slashes. Addressed in #7982.
Features:
.click(),.dblclick(), and.rightclick()now accept optionsaltKey,ctrlKey,metaKey, andshiftKeyto hold down key combinations while clicking. Addresses #486.You can now chain
.snapshot()off ofcy.stub()andcy.spy()to disabled snapshots during those commands. For example:cy.stub().snapshot(false). Addresses #3849.
Bugfixes:
The error
Cannot set property 'err' of undefinedwill no longer incorrectly throw when rerunning tests in the Test Runner. Fixes #7874 and #8193.Cypress will no longer throw a
Cannot read property 'isAttached' of undefinederror duringcypress runon Firefox versions >= 75. Fixes #6813.The error
Maximum call stack size exceededwill no longer throw when callingscrollIntoViewon an element in the shadow dom. Fixes #7986.Cypress environment variables that accept arrays as their value will now properly evaluate as arrays. Fixes #6810.
Elements having
display: inlinewill no longer be considered hidden if it has child elements within it that are visible. Fixes #6183.When
experimentalShadowDomSupportis enabled,.parent()and.parentsUntil()commands now work correctly in shadow dom as well as passing a selector to.parents()when the subject is in the shadow dom. Fixed in #8202.Screenshots will now be correctly taken when a test fails in an
afterEachorbeforeEachhook after the hook has already passed. Fixes #3744.Cypress will no longer report screenshots overwritten in a
cy.screenshot()onAfterScreenshotoption as a unique screenshot. Fixes #8079.Taking screenshots will no longer fail when the screenshot names are too long for the filesystem to accept. Fixes #2403.
The "last used browser" will now be correctly remembered during
cypress openif a non-default-channel browser was selected. Fixes #8281.For TypeScript projects,
tsconfig.jsonwill now be loaded and used to configure TypeScript compilation of spec and support files. Fixes #7006 and #7503.reporterStatsnow correctly show the number of passed and failed tests when a test passes but theafterEachfails. Fixes #7730.The Developer Tools menu will now always display in Electron when switching focus from Specs to the Test Runner. Fixes #3559.
Documentation Changes:
We have a new guide on Test Retries.
Our Migration Guide has a new section for 5.0 migration.
Misc:
Cypress now uses the webpack preprocessor by default to preprocess spec files.
The Runs tab within the Test Runner has a new improved design when the project has not been set up or login is required. Addressed in #8141.
The type for the
Windowobject returned fromcy.window()is now correct. Addresses #7856.The type definition for Cypress's
ApplicationWindowcan now be extended. Addresses #7856.The type definition for
reporterOptionshas been added. Addresses #7877.
Dependency Updates
Upgraded Chrome browser version used during cypress run and when selecting Electron browser in cypress open from
80to83. Addressed in #7791.Upgraded bundled Node.js version from
12.8.1to12.14.1. Addressed in #7791.Upgraded
chalkfrom2.4.2to4.1.0. Addressed in #7650.Upgraded
cli-table3from0.5.1to0.6.0. Addressed in #7650.Upgraded
electronfrom8.3.1to9.2.0. Addressed in #7791 and #8235.Upgraded
execafrom1.0.0to4.0.2. Addressed in #7650.Upgraded
expressfrom4.16.4to4.17.1. Addressed in #8179.Upgraded
fs-extrafrom8.1.0to9.0.1. Addressed in #7650.Upgraded
log-symbolsfrom3.0.0to4.0.0. Addressed in #7650.Upgraded
tmpfrom0.1.0to0.2.1. Addressed in #7650.
- 4.x
4.3.0
5 Dec 2025Errors shown in the Test Runner have a new design including an expandable stack trace, better highlighting of code elements, and 'Learn more' links that link to relevant Cypress documentation. This is part of our larger improvements to error display with more exciting features to come. Addresses #3762.
When you open a Cypress project, clicking on the Settings tab and clicking into the Experiments panel will display the experimental features that are available and whether they are enabled for your project.
Added support for setting cookie
sameSitevalues viacy.setCookie(). Addresses #2437.
Released 3/30/2020
Features:
Errors shown in the Test Runner have a new design including an expandable stack trace, better highlighting of code elements, and 'Learn more' links that link to relevant Cypress documentation. This is part of our larger improvements to error display with more exciting features to come. Addresses #3762.
When you open a Cypress project, clicking on the Settings tab and clicking into the Experiments panel will display the experimental features that are available and whether they are enabled for your project.
Added support for setting cookie
sameSitevalues viacy.setCookie(). Addresses #2437.Added experimental support for adding
sameSitevalues to the objects yielded fromcy.setCookie(),cy.getCookie(), andcy.getCookies(). Users can enable this by setting theexperimentalGetCookiesSameSiteconfiguration value totrue. In Cypress 5, this will be the default. Addresses #2437.Added support for the
SameSitecookie attribute incy.request(),cy.visit(), and proxied HTTP requests. Addresses #6757.When an assertion is retried (using
.should()) and fails, it now shows the diff in thestdout. Addresses #6722.
Bugfixes:
Fixed a regression in 4.2.0 where cypress installation could fail if Git is not installed. Fixes #6752.
Fixed a regression in 3.5.0 where certain HTTP requests could fail with
Parse Error: Invalid header value charorParse Error: Header overflow. Fixes #5602.Fixed a regression in 4.2.0 where Electron deprecation warnings were printed to stderr in open mode. Fixes #6750.
Cookies set with a Domain containing an unknown TLD are now sent along for all requests. For example, a cookie like
foo=bar; Domain=.cypress.testwill now be sent during cy.request() tohttp://local.cypress.test. Fixes #6628.We fixed a situation where a cross-origin errors could incorrectly throw in Chrome. Fixes #5270.
Visibility checks against
vue-fragmentelements no longer throw an unexpected error. Fixes #6745.The stack trace is now properly shown in the console when clicking the command for tests having an
.onlythat throw an error. Fixes #6744.firefoxGcIntervalcan now correctly be set tonull. Fixes #6825.Cypress will no longer crash the process if an empty video chunk is received. Addressed in #6818.
Assertions failures on DOM elements no longer show unexpected diffs when they weren't retried. Fixes #6723.
Misc:
Security warnings no longer show in Mac OS when opening Cypress since our application now undergoes notarization from Apple. Addresses #5791.
The previously used spec filter in the Test Runner is now saved and restored for projects without an ID. Addresses #6739.
We collect more env information from Travis builds for potential use in the Cypress Dashboard. Addresses #6808.
We now collect env information from Netlify builds (for example when using {% url "cypress-io/netlify-plugin-cypress" github.com/cypress-io/netlify-plugin-cypress) to send along to the Cypress Dashboard. Addresses #6780.
Type added for
tagproperty when using Module API. Addresses #6795.We're continuing to make progress in converting our codebase from CoffeeScript to JavaScript. Addresses #2690 in #6833.
Dependency Updates
Upgraded Chrome browser version used during
cypress runand when selecting Electron browser incypress openfrom80.0.3987.141to80.0.3987.158. Addressed in #6855.Upgraded
electronfrom8.1.1to8.2.0. This bumps the bundled Chromium to80.0.3987.158. Addressed in #6855.Upgraded
@benmalka/foxdriverfrom0.2.3to0.3.0. Addressed in #6592.Upgraded
@cypress/get-windows-proxyfrom1.6.0to1.6.1. Addressed in #6823.Upgraded
execafrom1.0.0to4.0.0. Addressed in #6013.Upgraded
extract-zipfrom1.6.7to1.7.0. Addresses #6845 in #6845.Upgraded
firefox-profilefrom1.3.0to1.3.1. Addressed in #6594.Upgraded
get-portfrom5.1.0to5.1.1. Addressed in #6854.Upgraded
mimefrom1.6.0to2.4.4. Addressed in #6764.Upgraded
minimistfrom1.2.2to1.2.5. Addressed in #6747.Upgraded
squirrellyfrom7.7.0to7.9.2. Addressed in #6735.
4.2.0
3 Dec 2025Videos can now be recorded when running Electron in
--headedmode. Addresses #1767.cypress cache listnow prints the last time the cached binary was accessed for each version present. Addresses #6682.
Released 3/16/2020
Features:
Videos can now be recorded when running Electron in
--headedmode. Addresses #1767.cypress cache listnow prints the last time the cached binary was accessed for each version present. Addresses #6682.
Bugfixes:
We fixed a regression in 3.8.3 where HTTPS requests could experience slowdown. Fixes #6659.
We now detect some installations of Firefox that were previously undetected. Fixes #6669.
We fixed a race condition where an asynchronous error could fail to be caught when running the plugins file process. Fixes #6570.
We now more thoroughly ensure the parent of an element exists when recursively calling actionability checks in order to prevent some maximum call stack errors. Fixes #6707.
Specfiles containing
&or%characters now correctly run instead of erroring. Fixes #4210.We added support for running tests on Jira plugins even when Jira scripts were not minified. Fixes #1436.
We fixed a bug causing specs to hang after rerunning tests during
cypress openwhen there was an exception if thrown in anafterhook. Fixes #6619.cypress verifyno longer incorrectly prints messaging about this being the first time using that Cypress version. Fixes #6607.Screenshots no longer fail to be taken in Electron when Cypress
DEBUGlogs are enabled. Fixes #6662.
Misc:
A warning is now printed when setting the reserved key
CYPRESS_INTERNAL_ENVto a non-production value. Addresses #6436.When DEBUG logs are printed from
cypress:launcher, they now print a clearer log during browser detection for easier reading. Addresses #6700.The Test Runner now renders ANSI colors when there is a syntax error in the spec file. Addresses #6533.
The Test Runner now has an icon indicating whether the specs list parent folder is collapsed. Addresses #6277.
There's better type information for
.click,.dblclick, and.rightclickcommand'spositionargument. Addresses #6341.There's a more robust type signature for
.its()and.invoke(). Addresses #6431.Using
Cypress.dom.isDetachedno longer throws a type error in TypeScript projects. Addresses #4408.Using
cy.clearLocalStorage({ log:false })no longer throws a type error in TypeScript projects. Addresses #6615.We added types for
Cypress.sinon. Addresses #6720.We've added the foundational work required to support experimental features in the Test Runner. Addresses #6257.
Dependency Updates
Upgraded Chrome browser version used during
cypress runand when selecting Electron browser incypress openfrom78to80. Addressed in #6555.Upgraded
electronfrom7.1.13to8.1.1. This bumps the bundled Chromium to 80.0.3987.141 and the bundled Node to 12.13.0. Addressed in #6555.Upgraded
@ffmpeg-installer/ffmpegfrom1.0.19to1.0.20. Addressed in #6686.Upgraded
minimistfrom1.2.0to1.2.2. Addressed in #6726.Replaced deprecated
requestwithcypress-io/request. Addressed in #6679.
4.1.0
14 Aug 2025There is a new
cypress infocommand to see the locally detected browsers and other information related to Cypress. Addresses #4540.You can now click a 'Try Again' button to recheck if the server at the designated
baseUrlis running within the warning message duringcypress open. Addresses #3284.The plugins file function's
configargument now includesprojectRoot(absolute path to the root of the project) andconfigFile(absolute path to the configuration file). Addresses #5941.
Released 2/28/2020
Features:
There is a new
cypress infocommand to see the locally detected browsers and other information related to Cypress. Addresses #4540.You can now click a 'Try Again' button to recheck if the server at the designated
baseUrlis running within the warning message duringcypress open. Addresses #3284.The plugins file function's
configargument now includesprojectRoot(absolute path to the root of the project) andconfigFile(absolute path to the configuration file). Addresses #5941.
Bugfixes:
Fixed a regression where Cypress could throw a "Maximum call stack size exceeded" error when transmitting a circular object over the internal WebSocket. Fixes #6582.
We fixed an issue where using Chromium-family browsers could cause Cypress to throw a "WebSocket is not open: readyState 3" error under certain conditions. Fixes #5685.
We now more thoroughly ensure the parent of an element exists when recursively calling visibility and existence checks in order to prevent some maximum call stack errors. Fixes #4373.
We fixed an issue where a maximum call stack error would throw in some circumstances when
xhr.onreadystatechangeis accessed. Fixes #5864.We fixed a regression in 3.5.0 where typing into an iframe with a body element with the contenteditable attribute would throw an error. Fixes #5930.
We now set the default window size when running Chrome headlessly to 1280x720. Fixes #6210.
We fixed an issue where
cypress installwould not complete on Node.js 8.0.0. Fixes #6512 and #6568.{% url "
cy.clearLocalStorage()" clearlocalstorage now properly accepts thelogoption to disable logging. Fixes #6342.
Misc:
The error messages displayed when rerouting to a non same-origin domain has been updated to more accurately reflect the rules around same-origin policy. Addresses #6048.
We fixed an error message that would display the wrong available browser families during validation. Addressed in #6517.
We fixed some typos in some of our error messages. Addressed in #6508.
We're collecting more environment variables when running Cypress with GitLab CI. Addresses #6231.
The typing of
cy.$$has been updated to distinguish differences between it andCypress.$. "More info here" $#Cypress-vs-cy Addresses #2027.We're continuing to make progress in converting our codebase from CoffeeScript to JavaScript. Addresses #2690 in #6552, #6523, and #6545.
Dependency Updates
Upgraded
electronfrom7.1.10to7.1.13. Addressed in #6566.
4.0.0
8 Aug 2025- Breaking
The
--browserflag no longer acceptscanaryas its sole argument to run Chrome Canary. You now have to specifychrome:canaryto use the Chrome Canary browser. Addresses #6243. - Breaking
Installing Cypress on your system now requires Node.js 8+. Addresses #5632.
Released 2/6/2020
Summary:
Cypress 4.0.0 includes support for Mozilla Firefox browsers (beta support) and Microsoft Edge (Chromium based) browsers which is a big step forward for Cross Browser Testing in Cypress. We've also updated many of the underlying tools behind Cypress that bring new powerful features.
Breaking Changes:
:warning: Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 4.0.
Mocha, Chai, and Sinon.JS has been upgraded which includes a number of breaking changes and new features. Addresses #2528, #2529, #2866.
During
before:browser:launch, we no longer yield the second argument as an array of browser arguments and instead yield anoptionsobject with anargsproperty in order to support more advanced browser launch options. Addresses #6306.We updated the Cypress browser objects of all Chromium-based browsers, including Electron, to have
chromiumset as theirfamilyfield. Addresses #6243.- Breaking
The
--browserflag no longer acceptscanaryas its sole argument to run Chrome Canary. You now have to specifychrome:canaryto use the Chrome Canary browser. Addresses #6243. cy.writeFile()now yieldsnullinstead of the contents written to the file in order to more align with the behavior offs. Addresses #2466.- Breaking
Installing Cypress on your system now requires Node.js 8+. Addresses #5632.
Cypress no longer support CJSX. Addresses #3469.
Features:
Mozilla Firefox browsers now have beta support. Addresses #1096.
Microsoft Edge (Chromium based) browsers are now supported. Addresses #5433.
There is a new
Cypress.isBrowser()utility function. Addresses #2023.We updated the
Cypress.browserobject with a newchannelproperty which contains the release channel of the detected browser. Addresses #6243.Appending
.onlyto multiple tests or suites will now run all tests with the.onlyproperty. Addresses #2828.The
isFiniteassertion is now supported. Addresses #5669.The
emptyassertion is now supported when used against Map objects. Addresses #6072.The
nestedassertion chainer property is now supported. Addresses #3080 and #5004.
Bugfixes:
A test or suite appended with an
.onlywhen multiple tests or suites contained the same title now run correctly. Fixes #5345.The
.its()command now properly supports 0 as a value for indexes or object keys. Fixes #6216.
Documentation Changes:
Added Cross Browser Testing Guide with helpful CI strategies to consider when running tests across multiple browsers.
Added
Cypress.isBrowser()doc.
Misc:
We now pass through errors caused when attempting to read arguments passed through
config. Addresses #6279.We fixed a broken 'Learn more' link within the Node.js Version panel of the Test Runner Settings. Addresses #6237.
The browser icons in the Test Runner now display as images with the proper branding. Addresses #6188.
We updated the styling of browser dropdown in the Test Runner to look more like a button. Addresses #6298.
The timer in the Test Runner now always displays at a consistent length. Addresses #6168.
You can print debug information about the memory & CPU usage of Cypress, which can be accessed by enabling the
cypress:server:util:process_profilerdebug stream. Addresses #6169.We added types for plugin events. Addresses #6322.
Dependency Updates
Added
@benmalka/foxdriver. Addressed in #1359.Upgraded
@cypress/browserify-preprocessorfrom1.1.2to2.1.1. Addressed in #4308 and #4226.Upgraded
bluebirdfrom3.5.0to3.7.2. Addressed in #4226.Upgraded
cachedirfrom1.3.0to2.3.0. Addressed in #4208 and #4226.Upgraded
chaifrom3.5.0to4.2.0. Addressed in #2862 and #4226.Upgraded
chai-as-promisedfrom6.0.0to7.1.1. Addressed in #4226.Upgraded
chalkfrom2.4.0to3.0.0. Addressed in #4226.Upgraded
commanderfrom2.15.1to4.0.1. Addressed in #4208 and #4226.Upgraded
debugfrom2.15.1to4.0.1. Addressed in #4226.Upgraded
execafrom0.10.0to3.3.0. Addressed in #4226.Added
firefox-profiler. Addressed in #1359.Added
foxdriver. Addressed in #1359.Upgraded
fs-extrafrom5.0.0to8.1.0. Addressed in #4226.Upgraded
getosfrom3.1.1to3.1.4. Addressed in #4226.Upgraded
is-cifrom1.2.1to2.0.0. Addressed in #4226.Upgraded
mochafrom2.5.3to7.0.1. Addressed in #2703 and #4226.Upgraded
listrfrom0.12.0to0.14.3. Addressed in #4226.Upgraded
log-symbolsfrom2.2.0to3.0.0. Addressed in #4226.Added
marionette-client. Addressed in #1359.Upgraded
ramdafrom0.24.1to0.26.1. Addressed in #4226.Upgraded
sinonfrom3.2.0to8.1.1. Addressed in #2881 and #4226.Upgraded
strip-ansifrom3.0.1to6.0.0. Addressed in #1359.Added
systeminformation. Addressed in #1359.Upgraded
support-colorsfrom5.5.0to7.1.0. Addressed in #4208 and #4226.Upgraded
untildifyfrom3.0.3to4.0.0. Addressed in #4226.
- 3.x
3.0.0
8 Jan 2025- Removed
screenshotOnHeadlessFailurehas been removed as an option incypress.json. Instead you can now control this behavior directly with code by settingscreenshotOnRunFailuretofalsewithin the new Screenshot API. Fixes #1140 and #1754. There is a new cy.task() command that enables you to go outside the browser to perform tasks directly in
node. This will make it easy to setup, scaffold, seed, talk to your database, or anything else useful on a backend.cy.screenshot() has been rewritten from the ground up. It now takes a screenshot of only the application under test by default. It also can take full page screenshots or element only screenshots. This is the first step of Cypress Dashboard support for screenshot diffing.
Released 5/29/2018
Summary:
There is a new cy.task() command that enables you to go outside the browser to perform tasks directly in
node. This will make it easy to setup, scaffold, seed, talk to your database, or anything else useful on a backend.cy.screenshot() has been rewritten from the ground up. It now takes a screenshot of only the application under test by default. It also can take full page screenshots or element only screenshots. This is the first step of Cypress Dashboard support for screenshot diffing.
When running with
cypress runwe now run each spec file in isolation from others. We have rewritten our reporter to provide more details and provide a summary of the run at the bottom.The Dashboard has been upgraded to make it easier to understand the results of each spec run. This was done in anticipation of providing you the ability to parallelize and load balance your spec files automatically in CI.
We are now capturing the performance and timings data of every test when using
--recordmode and are beginning to offer the first analytics and insights into the health of your tests on our Dashboard service.Cypress now caches globally per version which prevents it from being installed multiple times across projects.
Breaking Changes:
We now run each spec file in isolation from one another. This shouldn't technically break anything, but if you have set up your tests in a way that requires the state of a previous spec file, this could potentially break your tests. This will go a long ways towards reducing problems we were seeing with long runs in CI. Fixes #431, #681, #1589, #1539, and #1692.
The environment variable
CYPRESS_BINARY_VERSIONhas been removed. You should use the equivalent environment variableCYPRESS_INSTALL_BINARYinstead.The environment variable
CYPRESS_SKIP_BINARY_INSTALLhas been removed. To skip the binary install, setCYPRESS_INSTALL_BINARY=0.- Removed
screenshotOnHeadlessFailurehas been removed as an option incypress.json. Instead you can now control this behavior directly with code by settingscreenshotOnRunFailuretofalsewithin the new Screenshot API. Fixes #1140 and #1754. trashAssetsBeforeHeadlessRunshas been renamed totrashAssetsBeforeRunsin our configuration. Fixes #1754.videoRecordinghas been renamed tovideoin our configuration to be clearer and prevent confusion about recording to our Dashboard. Fixes #562.Cypress no longer copies screenshots and videos to artifacts for CircleCI. Copying artifacts should be left up to the user to handle themselves in their
circle.ymlfile. Fixes #1592.The standard output has been redesigned to better visualize spec files running in isolation and to be more visually appealing. This may break any specialized logic written that expected the standard output to be structured in a specific way or contain specific words. Fixes #1588.
cy.screenshot() no longer takes a screenshot of the runner by default. Instead it will hide the runner, remove application scaling and then scroll to take a full page picture of your application.
beforeandafterhooks within a support file now run before/after every spec file, instead of only once before/after the entire run. #681
Features:
There is a new cy.task() command for executing any arbitrary
nodecode.You can now run multiple specs by passing a glob to the
--specargument ofcypress run. Fixes #263, #416 and #681.There is a new Screenshot API and new cy.screenshot() options that allow you set defaults for how screenshots are captured, whether to scale your app, disable timers and animations, or which elements to black out in the screenshot. You can also set defaults for whether to automatically take screenshots when there are test failures or whether to wait for the Command Log to synchronize before taking the screenshot. Fixes #1424.
cy.screenshot() can now be chained off of commands that yield a DOM element and will only take a screenshot that element.
During install of cypress, the Cypress binary is now downloaded to a global cache. This prevents multiple projects from downloading the same Cypress version. Fixes #1300.
The seeded
example_spec.jsfile has been replaced by anexamplesfolder with several spec files. This more closely reflects the recommended use of Cypress - as smaller groups of tests split among many files that will now be run in isolation. The tests were also updated from ES5 to ES6. You can see all changes in thecypress-example-kitchensinkrepo Fixes #1460.Cypress now watches all the
plugins file's entire dependency tree to make iterating on plugins easier. Fixes #1407.Videos will now be saved locally with a filename named after the associated
specfile that it represents. Fixes #980.The Test Runner now displays
skippedtests differently thanpendingtests. #244.Standard output now displays the number of
skippedtests within the summary output duringcypress run. #1559.The url to view the run in the Dashboard is now printed to output during
cypress run. #494.We now print the browser and browser version run in the output during
cypress run. #833.The build number and url to CI for tests run within Drone are now captured and displayed on the run within the Dashboard. #1709.
Bugfixes:
Cypress no longer crashes when attempting to proxy a websocket connection that fails. Fixes #556.
Asserting that an attribute equals a falsy value no longer fails when the value was falsy. Fixes #831 and #1491.
Snapshots now ignore stylesheets with
media="print". Fixes #1568.Fixed issue where the Cypress
windowwas being returned instead of AUT'swindow. Fixes #1436.The
closeevent now properly fires onfilewhen manually closing the browser. Fixes #1560.cypress.env.jsonis now being watched for changes. Fixes #1464.Fixed issue when using TypeScript that caused namespace errors to be thrown. Fixes #1627.
Fixed error message on
.type()and.clear()when typing into non-typeable elements or clearing non-clearable elements to accurately list the elements allowed. Fixes #1650.Added Chrome flag
--disable-blink-features=RootLayerScrollingto prevent the application under test from "shaking" in recent versions of Chrome. Fixes #1620.Fixed issue where some TTY characters were not properly formatted in the terminal for Windows during
cypress run. Fixes #1143 and #1550.Removed an extraneous error display from Electron during
cypress runabout a "transparent titlebar" setting. Fixes #1745.
Misc:
We are now aggressively turning on colors when running in CI. If you're using Jenkins and do not have an ANSI color plugin installed, you can turn off colors with the
NO_COLOR=1environment variable. Fixes #1747 and #1748.When running
cypress run --recordon forked PR's, we now detect that the Record Key is missing and do not fail the build. We will display a warning, but continue running the tests. Fixes #1193.Searching in the Test Runner now filters out any non-matching folders. Fixes #1706.
Duplicate, subsequent logs in the Command Log are now collapsed and can be expanded to view all logs. Fixes #1580.
We now throw a descriptive error if an alias using
.as()was defined starting with the@character. #1643.We now pass the
--disable-device-discovery-notificationsflag automatically. This should prevent Chromium browser from automatically trying to communicate with devices in your network, such as printers, while running tests. Fixes #1600.We now pass any reporter errors along and provide a stack if a custom reporter you've provided does not exist. Fixes #1192.
You can now pass a normal object to
cypress.open()orcypress.run()through the Module API, just as you would from the command line. #1442.Added type definitions for
Cypress.offandCypress.log. Fixes #1110 and #1591.Update type definitions for cy.screenshot() to reflect new changes to command's options. Fixes #1753.
The type definition for .filter() now correctly supports a function argument.
The type definition for .scrollIntoView() no longer errors when passed a
durationoption. Fixes #1606.NODE_OPTIONSenvironment variables now print within thecypress:clilogs when running inDEBUGmode. Although usingNODE_OPTIONSthemselves should not be used due to #1676. Fixes #1673.Cypress will error and exit with status 1 if no specs were found during
cypress run. Fixes #1585.We are now counting and aggregating the stats at the end of test runs separately from Mocha. Cypress considers a test to be the
itand any accompanyinghooksthat run before or after a test. Cypress will correctly associate failures in those hooks to the test itself. We believe this more accurately models and just "makes sense". Fixes #1163.The minimum viewport size has been lowered from
200pixels to20pixels. Fixes #1169 and #1444.Internal changes to our API structure and communication. Fixes #1170, #1413, #1415.
We output a much more complete test results object when using cypress as a module. Fixes #1248.
Added keywords to Cypress NPM package. Fixes #1508.
Centered the animating icon in the Test runner when 'running'. Fixes #1695.
We made some changes to internal references of
headedandheadlessto be more specific and instead referencerun modeandinteractive mode. Fixes #1140.The test name text is now selectable inside the Command Log. Fixes #1476.
Minor improvements to contributing docs and scripts. Fixes #1665.
We now collect Semaphore CI params and provide URL's to click into the builds from the Dashboard. Fixes #1785.
Config overrides coming from the CLI or environment variables are now validated the same way as if they've been set in
cypress.json. Fixes #1783.There is a better / more helpful experience around passing unknown options to the CLI. Fixes #837.
Display an empty message when there is no commit information on recorded runs. Fixes #1809.
Documentation Changes:
Update
cy.screenshot()doc to include new accepted usage and optionsUpdate
Installing Cypressdoc to include new options for Cypress binary cachingUpdated
Writing and Organizing Teststo include newly seededexamplesfolderUpdated
Launching Browsersto include our disabling of device discovery notificationsUpdated
Preprocessorsto reflect all wayscloseevent could be triggeredUpdated use of "running headlessly" to more accurate "during
cypress run"
- 2.x
2.1.0
30 Aug 2022The Selector Playground has been updated to automatically prefer
data-cy,data-testordata-testidattributes when providing the unique selector for an element. Additionally it now exposes a public API that you can use to control how it determines which selector to use. Fixes #1135.
Released 3/1/2018
Bugfixes:
Prevent a bug with
node-sasson OSX + Windows when localnodeversion does not match bundlednodewhen importing components directly in spec files. The underlying issue was because we forgot to updateBuildkiteandAppveyorwhen we upgradedElectronin2.0.0. Fixes #1387 and #1390.
Features:
The Selector Playground has been updated to automatically prefer
data-cy,data-testordata-testidattributes when providing the unique selector for an element. Additionally it now exposes a public API that you can use to control how it determines which selector to use. Fixes #1135.
Documentation Changes:
2.0.3
17 Aug 2022The runner no longer appears to "hang" if a
beforehook fails in a test with siblings. Previously the test would never generate astatusand look pending forever. This was a visual bug only. Fixes #1343.The Desktop GUI properly renders folders that contain specs in Windows now. Fixes #1335.
The viewport dropdown helper in the Runner now displays string quoted JSON instead of an object literal. This better matches how you should write those options in
cypress.json. Fixes #1350.
Released 2/21/2018
Bugfixes:
The runner no longer appears to "hang" if a
beforehook fails in a test with siblings. Previously the test would never generate astatusand look pending forever. This was a visual bug only. Fixes #1343.The Desktop GUI properly renders folders that contain specs in Windows now. Fixes #1335.
Misc:
The viewport dropdown helper in the Runner now displays string quoted JSON instead of an object literal. This better matches how you should write those options in
cypress.json. Fixes #1350.
2.0.2
10 Aug 2022Fixed more edge cases where legitimate JavaScript code was being modified unexpectedly by the
modifyObstructiveCodeconfiguration. We've tightened up the regexp even more and added 40 popular JS libraries to test against to ensure they are not modified. Fixes #1334.Fixed an edge case when hooks such as
beforeEachorafterEachthrew an identical error message, Cypress would hang indefinitely and never finish running the tests. Fixes #674.Fixed bug when
Errorsthat threw with no arguments:throw new Error()and had their messages appended would duplicate the message over and over again. Fixes #1338.
Released 2/17/2018
Bugfixes:
Fixed more edge cases where legitimate JavaScript code was being modified unexpectedly by the
modifyObstructiveCodeconfiguration. We've tightened up the regexp even more and added 40 popular JS libraries to test against to ensure they are not modified. Fixes #1334.Fixed an edge case when hooks such as
beforeEachorafterEachthrew an identical error message, Cypress would hang indefinitely and never finish running the tests. Fixes #674.Fixed bug when
Errorsthat threw with no arguments:throw new Error()and had their messages appended would duplicate the message over and over again. Fixes #1338.
2.0.0
1 Jun 2022- Removed
Removed the flag
--disable-background-networkingfrom the Chrome launch args to fix problems in CI that would throttle XHR callbacks by up to 20-30 seconds. Fixes #1320. The built in default
Electronbrowser has been bumped from version53to59. This version represents the version ofChromiumthat Electron is using. In other words, runningcypress run(or viaElectron) will be like running your tests inChrome 59now. Although it is unlikely this would actually break any of your tests - it is technically possible they could behave differently. Fixes #895 and #891 and #823 and #860 and #1011 and #1252 and #1276.We are now detecting and automatically stripping code that obstructs Cypress from being able to test your application. Specifically, we are removing JavaScript code that tries to prevent clickjacking and framebusting. We have written very conservative rules that do their best to only strip these specific JS snippets, but it is technically possible that it may unintentionally rewrite valid JS if they match the regexp patterns. There is a new configuration option called
modifyObstructiveCodethat istrueby default. If you are experiencing problems after upgrading, you can turn this off and this will disable modifying your JS code. If you were using Cypress and upon visiting your website you would experience seemingly "random" redirects - these problems should now be eliminated. Fixes #886 and #1245 and #1064 and #992 and #692 and #352.
Released 2/15/2018
Breaking Changes:
The built in default
Electronbrowser has been bumped from version53to59. This version represents the version ofChromiumthat Electron is using. In other words, runningcypress run(or viaElectron) will be like running your tests inChrome 59now. Although it is unlikely this would actually break any of your tests - it is technically possible they could behave differently. Fixes #895 and #891 and #823 and #860 and #1011 and #1252 and #1276.We are now detecting and automatically stripping code that obstructs Cypress from being able to test your application. Specifically, we are removing JavaScript code that tries to prevent clickjacking and framebusting. We have written very conservative rules that do their best to only strip these specific JS snippets, but it is technically possible that it may unintentionally rewrite valid JS if they match the regexp patterns. There is a new configuration option called
modifyObstructiveCodethat istrueby default. If you are experiencing problems after upgrading, you can turn this off and this will disable modifying your JS code. If you were using Cypress and upon visiting your website you would experience seemingly "random" redirects - these problems should now be eliminated. Fixes #886 and #1245 and #1064 and #992 and #692 and #352.We are now clearing the browser's disk cache each time it opens (before any tests run). This means that any files that have been cached from
Cache-Controlheaders will be cleaned and removed. In the future, we will expose a newcy.clearCache()method to provide finer grained control of clearing the cache on a per test basis. But for now, this is an improvement. Fixes #1124.The
--specoption is now normalized against the current working directorycwdinstead of the project that you are running Cypress in. That means passing a path from the command line to a spec file will now work even when the project path is notcwd. Fixes #1159.
Bugfixes:
blacklistHostswould occasionally not work if you were blacklisting a host that had previously cached a file. In this case, the browser would serve it from disk and not make an actual HTTP request. This issue has been solved by clearing the cache when the browser opens. Fixes #1154.blacklistHostsis now correctly accepted via the--configCLI flag.Spies and Stubs created with
cy.stub()andcy.spy()will now retry their assertions when utilized from an alias. Fixes #1156.Basic auth is working again in Chrome 63 and Chrome 64. We "for real" fixed it this time by adding auth headers automatically at the network proxy layer and bypassed the browser altogether. We automatically apply auth headers if you provide a username/password in the URL of a
cy.visit(url). We also added a newauthoption to specify theusername/passwordusingcy.visit(url, options). All of the requests that match the origin of theurlwill have theAuthorization: Basic <...>headers added. Fixes #1288.Fixed domain parsing failures when
localorlocalhostwas not used as atld. Fixes #1292 and #1278.- Removed
Removed the flag
--disable-background-networkingfrom the Chrome launch args to fix problems in CI that would throttle XHR callbacks by up to 20-30 seconds. Fixes #1320.
Misc:
We now properly display nested objects and arrays that come from
cypress.jsonin the Settings tab in the Desktop Application.There's now a proper "empty view" when you go to setup your project to record on our Dashboard and you have not created any Organizations. Fixes #1306.
Removed the message about private projects requiring a paid account in the future. There will be a free tier including private projects. Fixes #827.
We moved the location of the browser's disk cache. That means that if you've been using Cypress for a really long time - you may have built up quite a large existing cache (in the hundreds of
mb). Before upgrading, you should open the browser and then manually clear the Cache. Or - if you have already upgraded to2.0.0delete the following folders:OSX:
~/Library/Caches/CypressLinux:
~/.cache/CypressWindows:
%APPDATA%\Cypress\cy\production\browsers
- 1.x
1.4.2
29 Jun 2021Fixed not being able to visit URLs that used
*localhostsuch ashttp://app.localhost:8080. Fixes #451.
Released 2/4/2018
Bugfixes:
Fixed not being able to visit subdomains when using 2nd level sub domains. Fixes #1175 and #600.
Fixed not being able to visit private TLD's from the public suffix such as
github.io,gitlab.ioorherokuapp.com. These now all work correctly. Fixes #380 and #402 and #802 and #493 and #1161.Fixed not being able to visit URLs that used
*localhostsuch ashttp://app.localhost:8080. Fixes #451.Mochawesome now works correctly and outputs files in all versions. Fixes #551.
Mochawesome will exit correctly with code
1when a hook fails. #1063.Fixed some incorrect typings with TypeScript. Fixes #1219 and #1219.
Fixed bug with custom 3rd party mocha reporters relying on
test.titlePathbeing a function. Fixes #1142.Fixed typo in CLI deps error about Docker. Fixes #1136.
Prevent
NODE_ENVfrom being set toundefinedwhen parent process did not have it defined. Fixes #1223.
Misc:
1.4.1
29 Jun 2021Using
DEBUG=cypress:*now correctly outputs all debugging information on OSX and Linux. Previously output other thencypress:cliwas ignored due to the CLI ignoringstderrfrom the binary. Fixes #921.Windows now forcibly displays colors correctly to the terminal. Fixes #1127.
Released 12/26/2017
Bugfixes:
Using
DEBUG=cypress:*now correctly outputs all debugging information on OSX and Linux. Previously output other thencypress:cliwas ignored due to the CLI ignoringstderrfrom the binary. Fixes #921.stdoutis now captured correctly in Windows when recording to the Dashboard. Fixes #977 and issue #711.Windows now forcibly displays colors correctly to the terminal. Fixes #1127.
Misc:
TTYis now handled correctly for Linux and OSX. This means that CI providers which turned off colors due toTTYbeing false will now display colors again such as TravisCI. Fixes #1126.We now handle
xvfbexiting with a non zero status code and display that error to you. This should help with situations wherexvfbis misconfigured on the system. Fixes #1113.We've added debug output for
xvfbwhenDEBUG=cypress:xvfbis enabled. Helpful when diagnosing problems withxvfb. Fixes #1128.We've added more TypeScript documentation for
cy.*methods. Fixes #1117.When developing on Cypress, we now start the process through the CLI to bring it into parity with how it works when used in production. Fixes #838.
Upgraded various CLI dependencies that were flagged for security warnings. There wasn't an actual security problem - just static analyzers complaining. Fixes #1103.
1.4.0
25 Jun 2021There is now a Search Bar in the Desktop GUI that enables you to filter the list of specs. Helpful for projects with a ton of spec files. Fixes #1098.
Trying to log in to Cypress no longer causes the app to crash. This area has had many more tests added. Fixes #1093.
Released 12/19/2017
Features:
There is now a Search Bar in the Desktop GUI that enables you to filter the list of specs. Helpful for projects with a ton of spec files. Fixes #1098.
Bugfixes:
The seeded
example_spec.jsfile no longer fails in Windows on thecy.exec()test. It now conditionally runs a command appropriate for Windows. Fixes #1097.Trying to log in to Cypress no longer causes the app to crash. This area has had many more tests added. Fixes #1093.
Some minor improvements to TypeScript definitions around
.then(). Fixes #1084.The Selector Playground now works correctly in the Electron browser. Fixes #1086.
1.3.1
17 Jun 20211.3.0
26 May 2021Plugins now emit a
before:browser:launchevent exposing you the browser that will be launched and its launch arguments. This enables you to modify the arguments prior to launching the browser. You can also use these arguments to modify how Chrome runs and to also test Chrome extensions. Fixes #691 and #298.We have launched a "CSS Selector Playground", a new UI button in the Test Runner that enables you to highlight elements in your application and receive a unique selector. You can also find elements by their text content. These mimics
cy.get()andcy.contains()behavior. Additionally you can copy the generated Cypress command to your clipboard or output the generated selector to your console. This feature is in beta. It only works in Chrome (not in Electron). We are aware of some bugs in it, but it is good enough for use and feedback. Please check out issue #917, watch an animated gif demonstration, and leave any feedback you have there. Fixes #917.
Released 12/17/2017
Features:
Plugins now emit a
before:browser:launchevent exposing you the browser that will be launched and its launch arguments. This enables you to modify the arguments prior to launching the browser. You can also use these arguments to modify how Chrome runs and to also test Chrome extensions. Fixes #691 and #298.We have launched a "CSS Selector Playground", a new UI button in the Test Runner that enables you to highlight elements in your application and receive a unique selector. You can also find elements by their text content. These mimics
cy.get()andcy.contains()behavior. Additionally you can copy the generated Cypress command to your clipboard or output the generated selector to your console. This feature is in beta. It only works in Chrome (not in Electron). We are aware of some bugs in it, but it is good enough for use and feedback. Please check out issue #917, watch an animated gif demonstration, and leave any feedback you have there. Fixes #917.
Documentation Changes:
1.2.0
21 May 2021There is a new
blacklistHostsoption incypress.jsonthat allows you to block requests made to those hosts. Blocked requests will respond with a503status code. This is useful for blocking 3rd party domains like Google Analytics. We have added a new recipe demonstrating this. Fixes #442.
Released 12/14/2017
Features:
Plugins can now return a
Promiseand modify the yieldedconfigto set new configuration values and environment variables. Fixes #1042 and #909 and #576.There is a new
userAgentoption incypress.json. This enables you to change theuserAgentof the browser for the entire browsing session. Fixes #364.There is a new
blacklistHostsoption incypress.jsonthat allows you to block requests made to those hosts. Blocked requests will respond with a503status code. This is useful for blocking 3rd party domains like Google Analytics. We have added a new recipe demonstrating this. Fixes #442.Added chai assertions in TypeScript to generate autocompletion. Fixes #1073.
Bugfixes:
Updated TypeScript definitions to more accurately match the current Cypress API. Fixes #1050. Also note that if you were extending Cypress in TypeScript the
Chainerinterface changed. Please read 1048#issuecomment-351891910 to understand what you will need to update.
Misc:
Renamed
environmentVariablestoenvin the Desktop GUI. Fixes #1052.Cypress.config()now returns a complete set of configuration values. Fixes #509.Added TypeScript typings for bundled Cypress tools like
$,_, etc. Fixes #1046.Some error messages were made more passive. Fixes #1025.
Documentation Changes:
1.1.0
17 May 2021We have officially launched the new Plugins API interface. This adds a
cypress/plugins/index.jsfile to new and existing projects. Using this file will enable you to modify the internals of Cypress running in the backgroundnodeprocess. This means you will be able to usenodeAPI's that are executed outside of the browser.We have currently added only one event for modifying the test file preprocessor, but this paves the way for adding many more event types. You can now modify every aspect of how files are sent to the browser.
We have extracted the default
browserifypreprocessor into its own package - @cypress/browserify-preprocessor://github.com/cypress-io/cypress-browserify-preprocessor. This is bundled with Cypress, but it is extracted so it can be used / modified by you to change the default options we pass tobrowserify. Additionally, you can swap out this preprocessor for something else entirely.
Released 11/19/2017
Summary:
We have officially launched the new Plugins API interface. This adds a
cypress/plugins/index.jsfile to new and existing projects. Using this file will enable you to modify the internals of Cypress running in the backgroundnodeprocess. This means you will be able to usenodeAPI's that are executed outside of the browser.We have currently added only one event for modifying the test file preprocessor, but this paves the way for adding many more event types. You can now modify every aspect of how files are sent to the browser.
We have extracted the default
browserifypreprocessor into its own package - @cypress/browserify-preprocessor://github.com/cypress-io/cypress-browserify-preprocessor. This is bundled with Cypress, but it is extracted so it can be used / modified by you to change the default options we pass tobrowserify. Additionally, you can swap out this preprocessor for something else entirely.
Features:
There is now a Plugins API interface. Partially addresses #684.
We have added the first Plugin API event called:
file:preprocessor. Fixes #580 and #581.You can now customize the default babel configuration options for the
browserifypreprocessor. Fixes #343 and #905.CoffeeScript 2 is supported via modifying the default options for the
browserifypreprocessor. Fixes #663.You can swap out or extend the default preprocessor to do exotic things like compile ClojureScript into JavaScript. Fixes #533.
We have created a @cypress/webpack-preprocessor://github.com/cypress-io/cypress-webpack-preprocessor preprocessor NPM package for you webpack users (because we are nice ゚リノ). Fixes #676.
Bugfixes:
cy.contains(selector, regexp)now works as intended. Fixes #801.We no longer format fixtures in any capacity. This fixes a bug with improperly formatting fixtures in Windows. You should handle formatting fixtures yourself. Fixes #884 and #902.
cy.viewport()resolves if only width or only height changes. Fixes #873.Cypress now auto reloads when spec files are modified in Windows. Fixes #712.
Misc:
There is a new
--globaloption useful withcypress opento force Cypress to open in global mode. This is helpful when you have multiple nested Cypress projects but only want to install Cypress once in the root project. Fixes #889.The module API accepts
reporterOptionsas an object literal like it does for theenvandconfigproperties. Fixes #899.
Documentation Changes:
1.0.3
13 May 2021The Test Runner now enables you to collapse folders when displaying a list of specs. Fixes #760. Contributed
Released 10/29/2017
Features:
The Test Runner now enables you to collapse folders when displaying a list of specs. Fixes #760. Contributed
Bugfixes
The
onChangeevent callback for React now works (again) oninputtypenumberoremail. Fixes #816 and #770.Fixed error when recording and failing to parse the git commit message. Fixes #847 and #841.
Using a single space on:
cy.type(' ')now works. Fixes #807. Contributedcy.spread()can now be used on a collection of DOM elements. Fixes #735. ContributedCLI shows help message when it is invoked with an unknown command like
$(npm bin)/cypress foo. Fixes #641.
Misc:
Enable passing
CYPRESS_RECORD_KEYwithout using the CLI by invoking the binary directly. Fixes #820.Cypress binaries can now be pointed to a staging environment with
CYPRESS_ENV=staging. Fixes #813.The Test Runner displays the scrollbar correctly when the update banner is displayed. Fixes #803.
The branch name is now properly collected when recording in Buildkite CI. Fixes #777.
You can install the Cypress binary from any URL or file path using the
CYPRESS_BINARY_VERSIONenvironment variable. Closes #701.
Documentation Changes:
1.0.2
12 May 2021Reading the note…
1.0.1
12 May 20211.0.0
12 May 20211.0.0marks our transition out of a private beta and into a public beta. We've lifted all the restrictions for using Cypress. It is now accessible to everyone. Until we are out of beta, the Dashboard Service will continue to be free.We will continue to follow
semverfrom this point on (and also a bit more rigorously).Cypress is now open source! This project is licensed under the terms of the MIT License.
Released 10/09/2017
Summary:
1.0.0marks our transition out of a private beta and into a public beta. We've lifted all the restrictions for using Cypress. It is now accessible to everyone. Until we are out of beta, the Dashboard Service will continue to be free.We will continue to follow
semverfrom this point on (and also a bit more rigorously).Cypress is now open source! This project is licensed under the terms of the MIT License.
We have a Contributing Guideline to help contributors get started as well as issues labeled
first-timers-onlyfor those wanting to contribute right away.You can now use the Test Runner application without logging in. Some areas of the application still require logging in through GitHub, like the 'Runs' tab and viewing the project's 'Record Key'. The only places where login is required is when it interacts with our external servers. Naturally these places are optional and will not affect the local test writing + running experience.
We've removed the requirement of filling out an early adopter form and approval for logging in with GitHub to Cypress.
www.cypress.io has an all new design to help new visitors get started quickly and understand our future pricing more clearly.
We are still updating the docs to reflect the
1.0.0release.
Features:
Windows is now supported. We have been running it successfully on EC2 and all of our example projects are also running in CI with Appveyor. It is still super beta (we're aware of a couple issues already) and we're still updating our own infrastructure to manage and test it as comprehensively as we do OSX and Linux. We are only building a 32bit version of Windows, but will soon be building a 64bit as well. As of today the Windows binary is about 2x the size of what it will be. Unzipping takes a long time, we are sorry. Fixes #74 and #444.
Misc:
Added the
Betaflag everywhere (since we are still technically in beta).Reduced the frequency the app checked for updates. Fixes #713.
The CLI now sends
archparameter to the download server so we can build and serve multiple binaries for Windows + Linux.
Documentation Changes:
Added a 10 minute Getting Started video that Andrew Van Slaars://github.com/avanslaars created.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.