Cucumber Open

Cucumber Open runs automated acceptance tests from specifications written in plain language, helping teams check whether software behaves as described. It supports Behaviour-Driven Development by executing specifications written in Gherkin, which are stored in `.feature` text files, typically alongside software in source control. Step definitions connect Gherkin steps to code that performs them. Official implementations include JavaScript, Java, Ruby, Android Java, Kotlin, Scala, and C++; semi-official and unofficial implementations are also listed. Gherkin has variations for spoken languages, allowing teams to use keywords in their own language. Built-in report formatters include HTML, JSON, JUnit, and progress, and custom formatters are supported. Cucumber can run in continuous integration environments; its documentation describes JUnit output and a Jenkins reporting plugin. The project is open source and costs nothing. Published Cucumber Reports use public URLs without authentication and are deleted automatically after 24 hours; the report service says data is stored in U.S. data centers and encrypted at rest.

Cucumber Open links readable Gherkin specifications to executable steps and provides several reporting options. Teams using published Cucumber Reports should account for public report URLs and automatic deletion after 24 hours.

Cucumber Open may suit software teams that want executable acceptance specifications readable by both technical and nontechnical teammates. Its listed implementations and language variations can fit teams using different programming or spoken languages.

Cucumber Open suits teams that want product, QA, and engineering to work from the same readable acceptance specifications. Its central strength is linking those specifications to executable code; the trade-off is that teams still need programming-language implementations and step definitions.

Overview

Cucumber supports Behaviour-Driven Development by checking software against executable specifications. Those specifications use Gherkin and live in plain-text .feature files, typically alongside the software in source control. That keeps requirements reviewable as text, but the steps only run once connected to code through step definitions.

Founded in 2008, the project has returned to community ownership. The framework is open source, with a free plan at no cost. The project is funded by donations and sponsorships, alongside Tidelift and Ethical Ads. For teams comfortable with a community-supported project, that avoids a software license cost; it is not a substitute for a paid testing service.

Key features

Gherkin and step definitions

Gherkin has grammar flavours for spoken languages, so teams can use keywords in their own language. The benefit is a shared format for specifying expected behaviour; the limit is that readable steps do not remove the need to write and maintain code that performs them.

Official implementations cover JavaScript, Java, Ruby, Android Java, Kotlin, Scala, and C++, with semi-official and unofficial implementations also available. This gives teams several implementation choices, though the framework's usefulness depends on having an implementation that fits their stack.

Execution and reporting

Cucumber supports local execution, parallel execution, browser testing, and API access. Built-in report formatters produce HTML, JSON, JUnit, or progress output, and teams can add custom formatters. It can run in continuous integration; JUnit output and a Jenkins reporting plugin are documented options. These choices suit teams integrating acceptance tests into existing workflows rather than seeking a standalone hosted test runner.

Published Cucumber Reports have a material privacy limitation: report URLs are public and require no authentication, and reports are automatically deleted after 24 hours. Publishing is anonymous, with report data stored in US data centers and encrypted at rest. Teams handling sensitive test output should weigh public access carefully before publishing.

Pricing

Cucumber Open is open source and free: the Cucumber Open plan costs nothing and includes free Cucumber Reports. There are no paid tiers or seat and usage quotas in the plan. That makes it a straightforward fit for teams that can run the framework themselves; the trade-off is a framework and community support model rather than a paid service plan.

Platforms

Cucumber Open lists Android, API, Linux, macOS, and Windows support. Its published implementations span several programming languages, while execution can be local or integrated into continuous integration. Teams should choose based on whether an implementation fits their codebase, not just the platform label.

Who it's for

Cucumber Open is best for teams that want acceptance criteria readable across roles, but are prepared to maintain executable step definitions and integrate test runs into their own workflow. Its language flavours can help multilingual teams share specifications. It is a weaker fit for readers seeking visual authoring, a managed test service, or authenticated access to published reports.

Pros and cons

• Pros: Gherkin specifications are readable text files that can live with the software in source control, making them practical shared artifacts.
• Pros: Multiple official language implementations, custom formatters, and JUnit output provide options for fitting tests into varied codebases and CI workflows.
• Pros: The open-source framework and Cucumber Reports are free, with local and parallel execution supported.
• Cons: Step definitions require programming code, so Gherkin alone does not make test creation code-free.
• Cons: Published reports are publicly accessible without authentication and expire after 24 hours, which may rule them out for sensitive results.
• Cons: Support and learning are centered on documentation, books, Cucumber School, and community channels rather than a paid support plan.

Alternatives

For a broader comparison, see the BDD Testing Tools list.

• Serenity BDD is another free open-source choice, with Android, iOS, Linux, macOS, self-hosted, web, and Windows platforms. Its JUnit 4 support is deprecated and planned for removal in Serenity 6.0.0, so teams relying on JUnit 4 should factor in that transition.
• Kiwi is a free alternative for teams working on iOS or macOS.
• Concordion is a free Java library under Apache License 2.0, for teams seeking a Java-specific option across Linux, macOS, self-hosted, and Windows environments.
• FitNesse is a free open-source project with API, Linux, macOS, self-hosted, web, and Windows platforms.
• Ginkgo is a free Go testing framework for Linux, macOS, and Windows; its current supported major version is v2.
• BDDX offers a web-based free plan for up to 50 runs/month, then paid run tiers at $9.99 a month for up to 51-250 runs/month and $14.99 a month for up to 251-500 runs/mont.
• Behat is free software for Linux, provided without warranty.
• CukeTest is a freemium option for Linux, macOS, and Windows, with a free trial and a Lite plan that includes visual feature editing, JavaScript and Python, usage limits on some built-in automation libraries, and 500 automation API calls.

Verdict

Choose Cucumber Open if your team wants readable, source-controlled acceptance specifications that can execute in its existing code and CI workflows without a license cost. Its strongest reason to choose it is that bridge between shared Gherkin and executable tests; look elsewhere if you need visual authoring, managed execution, or private published reports.