Cypress vs Cucumber

From $75 per month (Cloud Team, month-to-month; $799/year works out at $67)

Free tier available

You only pay for Cypress Cloud. Team is $75 month-to-month or $799/year; Business is $3,199/year. Costs scale with recorded test results, so a large suite on every PR is the expensive shape.

Open source core. SmartBear sells CucumberStudio for collaborative scenario authoring, priced per user on request.

The test runner is free forever. Cypress Cloud free tier covers a limited number of recorded test results per month.

The Cucumber libraries are open source and free.

Category standard

Cypress.io · since 2017

Widely used

Smartbear · since 2008

• The interactive runner is the best onboarding experience in E2E testing; a new developer writes a passing test in minutes.
• Excellent documentation and one of the largest plugin ecosystems.
• Component testing and E2E in one tool with one config.

• Shared vocabulary between product, QA and engineering when the practice is actually followed.
• Scenarios double as living documentation that stays honest because it executes.
• Available in every major language.

• Runs in the same event loop as your app, which historically meant no multi-tab, multi-origin or iframe-heavy testing without workarounds. Support has improved but the model still constrains you.
• JavaScript and TypeScript only.
• Meaningful parallelisation effectively requires paying for Cypress Cloud.

• Almost always adopted as a syntax rather than a collaboration practice, at which point it is pure overhead on top of your real tests.
• The step-definition layer is a second codebase to maintain and refactor.
• Gherkin obscures technical detail that developers need when a test fails.

Front-end teams who value developer experience and live in a single-origin JavaScript app.

Teams genuinely practising BDD with three-amigos sessions, not teams who just want prettier test names.