✨ Introducing the new Free Parallelization Plan.Learn More

Eliminate Flaky Cypress Tests from CI

Save hours of test debugging using DOM, network, and console events captured by DeploySentinel from your CI.

Get Started

Or Book a Demo

Test Debugging - Network Request Failures

Trusted by quality-minded engineers at

Works with your CI & Cypress Test Suite, No Dashboard Required

An alternative to Cypress Dashboard, focused on providing the debugging tools engineers need.

DeploySentinel runs in your CI and integrates as a Cypress plugin.

Save Time & Sanity Fixing Tests in CI

Dive in beyond screenshots and video - time travel debug and leverage analytics to pinpoint the root cause of test failures

Inspect & Playback Full DOM Recordings

Using a browser inspect element tool to inspect DOM snapshots

Debug Network Payloads

Uncover Race Conditions with Test Timeline

and more...

Console Logs

View any console message emitted from your app, test, or browser.

Historic Test Trend

Determine historical test flakiness or errors for any test case in a single click.

Memory Metrics

Debug low-memory-induced flakes by tracking memory usage through test runs.

Custom Events

Enrich test runs with custom debug data such as DB snapshots.

Try the Debugger Live Demo

You can use your browser's dev tools and inspect the DOM snapshot.

Loading Demo...

Keep On Top of App & Test Suite Health

Get a birds-eye view on errors, flakes, slow tests, and common error messages all within a few clicks.

Track Test Suite Trends

Actionable Analytics Directly in Pull Requests

Accelerate Test Runs with Dynamic Parallelization

With DeploySentinel Dynamic Parallelization

Dynamic test parallelization with DeploySentinel

Without Parallelization

Why Engineering Teams Love DeploySentinel

Joe Gaudet

Director of Software Development

Debugging flaky tests using DeploySentinel has been a game changer for our team, allowing us to ship features quickly and confidently. The difference between simple videos is night & day.

Christopher Jamison

Lead QA Software Automation Engineer

Before working with you guys, I would run Cypress tests locally until I got tests to fail because the Cypress Dashboard didn't give enough information. With DeploySentinel, I no longer have to do that.

Get started in less than 2 minutes

Add our plugin with just 2 lines of code. Fully compatible with your existing Cypress test suite, no test changes necessary.

1. Install via NPM or Yarn

2. Import Support & Plugin File to Cypress

Cypress 10 and Above

Cypress 9 and Below

cypress.config.js
// Cypress Config File (cypress.config.js)
const { defineConfig } = require("cypress");
module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      // ❗ Must be declared at the top of the function to prevent conflicts
      [on, config] = require("@deploysentinel/cypress-debugger/plugin")(on, config);
    },
  },
});

cypress/support/e2e.js
1	1		`// Cypress Support File (cypress/support/e2e.js)`
	2	+	`import '@deploysentinel/cypress-debugger/support'; // ❗ Must be imported top of file`
2	3		`import './commands';`

3. Run Cypress with an API Key

Cypress Browser Type

Chrome / Chromium

Electron (Default)

Firefox / Edge (Coming Soon)

4. Parallelize Tests in CI (Optional)

For more parallelization configuration details, check out the parallelization docs.

Github Action

CircleCI

Jenkins

.github/workflows/e2e.yml
strategy:
  matrix:
    job: [0, 1, 2, 3]
steps:
  - name: Checkout
    uses: actions/checkout@v2
  - name: Install dependencies
    run: yarn install
  - name: Run Tests in Parallel
    uses: cypress-io/github-action@v4
    with:
      command: npx ds run --parallel --record --headless --browser chrome
    env:
      CYPRESS_DEPLOYSENTINEL_KEY: ${{ secrets.CYPRESS_DEPLOYSENTINEL_KEY }}

Debug Flaky Tests without Guessing

Start debugging test failures in CI for free with our 14 day free trial.

Start Free Trial

Product

Resources

Documentation Blog Support

Legal

Made with ♥ in San Francisco

cypress.config.js
1	1		`// Cypress Config File (cypress.config.js)`
2	2		`const { defineConfig } = require("cypress");`
3	3		`module.exports = defineConfig({`
4	4		`e2e: {`
5	5		`setupNodeEvents(on, config) {`
	6	+	`// ❗ Must be declared at the top of the function to prevent conflicts`
	7	+	`[on, config] = require("@deploysentinel/cypress-debugger/plugin")(on, config);`
6	8		`},`
7	9		`},`
8	10		`});`

.github/workflows/e2e.yml
	1	+	`strategy:`
	2	+	`matrix:`
	3	+	`job: [0, 1, 2, 3]`
1	4		`steps:`
2	5		`- name: Checkout`
3	6		`uses: actions/checkout@v2`
4	7		`- name: Install dependencies`
5	8		`run: yarn install`
	9	+	`- name: Run Tests in Parallel`
	10	+	`uses: cypress-io/github-action@v4`
	11	+	`with:`
	12	+	`command: npx ds run --parallel --record --headless --browser chrome`
	13	+	`env:`
	14	+	`CYPRESS_DEPLOYSENTINEL_KEY: ${{ secrets.CYPRESS_DEPLOYSENTINEL_KEY }}`