Cucumber vs Rainforest QA

Free tier available

Quote on request

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

Quote-based. Human-executed runs are billed separately from automated ones and are the expensive component.

The Cucumber libraries are open source and free.

Free tier for a small number of automated tests.

Widely used

Smartbear · since 2008

Emerging

Rainforest QA · since 2012

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

• The human fallback covers scenarios automation genuinely cannot reach.
• Anyone on the team can author a test.
• Results in minutes, integrated into the deployment pipeline.

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

• Human runs get expensive quickly at any real frequency.
• Human testers lack product context, so results need interpretation.
• Web only.

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

Teams that need broad release-gate coverage including flows nobody wants to automate.