Selenium WebDriver vs Cucumber

Free and open source

Free tier available

Free and open source. The real cost is grid infrastructure or a device-cloud subscription.

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

Everything, self-hosted

The Cucumber libraries are open source and free.

Category standard

Software Freedom Conservancy · since 2004

Widely used

Smartbear · since 2008

• The widest language and browser support of anything in the category, including legacy browser versions.
• A W3C standard, so it will outlive any single vendor. Skills transfer between employers.
• Every device cloud speaks Selenium, which keeps you portable between vendors.

• 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.

• No built-in waiting strategy, reporting, parallelism or assertions — expect to assemble and maintain a framework around it.
• Explicit waits are your problem, and getting them wrong is the number one source of flake in real Selenium suites.
• Out-of-process communication makes it slower than Playwright or Cypress.

• 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.

Enterprises with polyglot teams, legacy browser requirements, or an existing grid investment.

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