Sign in

We moved on from Cypress. Why haven't you?

The best teams are switching to Playwright. Currents is how they run it at scale.

See why teams switch to PlaywrightI'm on Playwright — show me Currents

These teams chose Playwright and trust Currents to run it at scale

  • Crunchbase
  • Autodesk
  • n8n
  • Apollo.io
  • Cursor

Why top teams are
switching to Playwright

  • Less Flakiness

    Playwright’s architecture reduces test flakiness by design. It runs tests in isolated browser contexts, uses native events (not simulated ones), and avoids Cypress’s common failure points like iframes, async chaining issues, and browser quirks. That means fewer reruns, faster feedback, and less time debugging CI-only failures.

    Teams are experiencing 15.60% less flakiness with Playwright.

  • Faster

    Cypress runs one test per process and takes seconds just to boot. Playwright’s lightweight runner executes multiple tests per machine in parallel, drastically reducing test duration and CI wait time.

  • Cheaper to run

    With faster feedback loops and fewer reruns due to flake, Playwright reduces both direct CI cost and indirect developer time waste.

    Ramp reduced their CI usage by 62%

  • Supports Safari (WebKit)

    • Cypress: Experimental support since 2022
    • Playwright: Built-in support for Chromium, Firefox, and WebKit (Safari)

    Teams looking to cover all major browsers cannot rely on Cypress.

  • Batteries included

    Playwright ships with native support for critical features like trace viewer, test retries, code coverage, accessibility testing, visual comparisons, and multi-tab flows — with no plugins, no configuration, and no paywalls.

    In contrast, Cypress lacks many of these features natively. Some are only available through community plugins (with maintenance risks), while others, like parallelization, flake detection, or advanced reporting are locked behind a paid plan.

  • Enterprise Ready

    Playwright is built on modern browser APIs with a flexible, low-level architecture that scales with your organization’s needs.

    Its open tooling, strong ecosystem, and growing community make it a safe long-term choice for engineering leaders who need reliability, extensibility, and control across large, distributed teams.

Case Studies

How to migrate

  1. Prepare Infrastructure

    Install Playwright and configure your CI pipeline.

  2. Setup Observability

    Use Currents to get visibility into test results and more.

  3. Write New Tests

    Write new tests in Playwright while still running Cypress.

  4. Gradual Replacement

    Start migrating existing tests, starting with flaky or slow tests.

Migration Timeline

  • 1

    Initial Setup (2-4 weeks)

    Infrastructure and core components

  • 3

    Gradual Migration (2-3 months)

    New tests in Playwright, migrate high-value tests

  • 4

    Final Phase

    Complete migration and optimization

AI-Powered Migration

Speed up your migration with AI tools that can help convert tests automatically:

  • Convert tests with AI tools like ChatGPT, Claude, Cursor, etc..
  • Grit.io for automated PR-based migration
  • Community tools for syntax conversion

Resources

FAQ

Still have unanswered questions?

Get in touch

Ready to join the Playwright side?

See what Currents can do for your Playwright test suite.

Explore Currents