Transform how you test with Cypress in CI

Cypress automatically balances your test specs across the available machines during parallelization. This ensures that your test specs run as fast as possible, with no need for manual configuration.

Accelerate your deployment times and quickly verify that your latest changes fixed a build in CI by automatically prioritizing the test specs that failed in the previous Cypress run.

Protect valuable CI resources by automatically canceling a Cypress run after a configurable numbers of tests fail. Auto Cancellation reduces CI costs and frees-up resources for other team members and builds.

Understand whether you've introduced or resolved failed, flaky, or pending tests. Analyze the impact of your branch's latest pull request by reviewing the before-and-after of test suite changes side-by-side.

Every test run error is captured, grouped, and accompanied by a detailed stack trace output that gives you the information you need to identify the exact point of failure in your application.

When a flaky test run is detected in CI, Cypress automatically flags the test run with the number of times it flaked in recorded history. Uncover previous flake occurrences and pinpoint when it was first detected.

Identify important changes that impact your test runs’ success and performance in CI. Analyze previous test failure rates, test definition changes, run durations, and flake occurrences with complete test history.

Ensure adequate test code coverage by tracking your total test suite size and runs over time. You can even filter by branch to fully understand which areas of your application might benefit from more test coverage.

Focus your time and resources on addressing the most chronically flaky tests in your test suite. Use Flaky Tests Analytics to prioritize flaky tests based on their recency, frequency, and severity.

Quickly surface the most commonly occurring error classes in your test suite. You can even read the exact error messages and understand how many tests are impacted by each error.

Create issues for failed tests on-the-fly and review historical issues using Cypress Cloud’s integration with Atlassian Jira — all from within the Cypress UI.

Improve your team’s collaboration, know exactly when a test fails, and give wider visibility into your test suite’s performance by integrating Cypress with Slack and Teams.

Integrate Cypress with your GitHub, GitLab, or Bitbucket source control to see test run results as commit status checks and pull/merge request comments.

Implement single sign-on so that you can fully control how your enterprise’s teams authenticate with Cypress.