> 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.md).

# Cypress

- [Your First Cypress Run](https://docs.currents.dev/getting-started/other-frameworks/cypress/you-first-cypress-run.md): Running Cypress tests in parallel with Currents Dashboard
- [Integrating with Cypress](https://docs.currents.dev/getting-started/other-frameworks/cypress/integrating-with-cypress.md): Overview of tools available for integrating cypress with Currents or Sorry Cypress
- [Compatibility](https://docs.currents.dev/getting-started/other-frameworks/cypress/integrating-with-cypress/compatibility.md): Integrating Cypress with Currents - compatibility table
- [Alternative Cypress Binaries](https://docs.currents.dev/getting-started/other-frameworks/cypress/integrating-with-cypress/alternative-cypress-binaries.md): Using alternative Cypress Binaries
- [CI Setup](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup.md)
- [Cypress - GitHub Actions](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-github-actions.md): Using GitHub Actions Matrix for parallelizing Cypress tests
- [Cypress - GitLab CI/CD](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-gitlab-ci-cd.md): Running Cypress test in parallel on GitLab
- [Cypress - Jenkins](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-jenkins.md): Running Cypress tests in parallel with Jenkins and Currents Dashboard
- [Cypress - CircleCI](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-circleci.md): Running Cypress tests in parallel on CircleCI and Currents dashboard
- [Cypress - Bitbucket Pipelines](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-bitbucket-pipelines.md): Running Cypress tests in parallel on Bitbucket Pipelines and Currents dashboard
- [Cypress - Azure DevOps](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-azure-devops.md): Running Cypress test in parallel on Azure DevOps and Currents Dashboard
- [Cypress - AWS Code Build](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-aws-code-build.md): Running Cypress in parallel on AWS CodeBuild
- [Cypress - NX](https://docs.currents.dev/getting-started/other-frameworks/cypress/ci-setup/cypress-nx.md): Running Cypress tests with NX
- [Troubleshooting Cypress](https://docs.currents.dev/getting-started/other-frameworks/cypress/troubleshooting-cypress.md): Troubleshooting Currents integration with Cypress


---

# 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.md?ask=<question>&goal=<user_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.
