> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/getting-started/other-frameworks/cypress/integrating-with-cypress/compatibility.md). # Compatibility Integrating Cypress with Currents - compatibility table {% hint style="warning" %} **We are suspending our support of Cypress test runner version 13+** We will continue to support [prior versions](/getting-started/other-frameworks/cypress/integrating-with-cypress/alternative-cypress-binaries.md) of Cypress. [Read more](https://currents.dev/posts/v13-blocking) {% endhint %} To report Cypress 13 and later results, upload them with `currents run upload`. See [Upload Cypress 13+ Results](/getting-started/other-frameworks/cypress/upload-cypress-13-results.md) and the [limitations of uploaded results](#limitations-of-uploaded-cypress-13-results). We provide several packages to integrate cypress runner with Currents (or Sorry Cypress) orchestration services: * ☁️ [cypress-cloud](https://github.com/currents-dev/cypress-cloud) - standalone runner for Sorry Cypress and Currents * \[deprecated] [cy2](https://github.com/sorry-cypress/cy2) - package for integrating arbitrary cloud orchestration services with cypress * \[deprecated] [@currents/cli](https://www.npmjs.com/package/@currents/cli) - a dedicated package for integrating cypress with Currents cloud service Please use the table below to select the version of the compatible package. #### Currents Customers
Cypress Version@currents/cli [deprecated]cypress-cloud
13.2.0+not supportednot supported
13.1.0not supportednot supported
12.6.0+ (Alternative Binaries)not supported1.4.1+
12.1.0+4.0.3+1.4.1+
12.0.0+3.1.3+1.4.1+
11.0.0+3.0.0+1.4.1+
6.7.0+any versionnot supported
#### Sorry Cypress Users
Cypress Versioncy2 [deprecated]cypress-cloud
13.2.0+not supportednot supported
13.1.0not supportednot supported
12.6.0+ (Alternative Binaries)not supported1.4.1+
12.1.0+4.0.6+1.4.1+
11.0.0+4.0.1+1.4.1+
6.7.0+any versionnot supported
#### **NX Users** NX users can use [@currents/nx](https://www.npmjs.com/package/@currents/nx) plugin to conveniently integrate Currents or Sorry Cypress with their project
Cypress@currents/nx
12.6.0+ (Alternative Binaries)2.0.0+
12.1.0+2.0.0+
12.0.0+0.2.1+
11.0.0+0.1.0+
6.7.0+any version
## Limitations of uploaded Cypress 13+ results Results uploaded with `currents run upload` come from files that Cypress writes after the run. Compared with `cypress-cloud`: * There is no orchestration. Split the spec files between CI machines yourself. * There is no live progress. The run appears when the upload runs. * The JUnit format keeps the last attempt of each test only, so tests are never flaky. Upload Cypress's run results (`cypress-json`) to keep every attempt. A test is flaky only when Cypress retries are enabled and it passed on a retry. * Cypress keeps the error of the last failed attempt only. Earlier failed attempts have no error message. * Cypress reports one duration for all attempts of a test. Each attempt gets an equal part of it. * There are no steps or command log. * A spec file that Cypress could not load, for example because of a syntax error, has no tests in the results. `currents run upload` prints a warning that names it, and the spec file is not in the run. * Uploading the results of a run again, for example by retrying the upload job, adds the screenshots and videos a second time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.currents.dev/getting-started/other-frameworks/cypress/integrating-with-cypress/compatibility.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.