Cucumber (software)

Cucumber (software)
source
Name	Cucumber
Developer	Aslak Hellesøy, SmartBear Software, Cucumber Ltd.
Released	2008
Programming language	Ruby, Java, JavaScript, Gherkin
Operating system	Linux, Microsoft Windows, macOS
Genre	Behavior-driven development
License	MIT License

Cucumber (software) is an open-source tool for behavior-driven development and executable specifications that enables collaboration among product owner, business analyst, software developer, quality assurance, and stakeholder roles. It parses plain-language descriptions written in the Gherkin domain-specific language to map human-readable scenarios to automated test code, integrating with JUnit, RSpec, TestNG, and Selenium-based test suites. Cucumber has influenced practices in agile ecosystems such as Scrum, Extreme Programming, and Kanban by promoting ubiquitous language and living documentation.

Overview

Cucumber originated as a tool to express acceptance criteria as executable examples, supporting a bridge between Agile, Behavior-driven development, ATDD, and TDD. Its core idea centers on mapping Gherkin steps to step definitions implemented in languages like Ruby, Java, JavaScript, Groovy, Scala, C# and integrating with frameworks such as Selenium, Appium, Capybara, and Puppeteer. The project ecosystem includes tooling for reporting, continuous integration with Jenkins, Travis CI, and GitLab CI/CD, and adapters for Maven, Gradle, npm, and Bundler package managers.

History and Development

Cucumber was created by Aslak Hellesøy in 2008 to implement ideas from Dan North, Dan North's behaviour-driven development and from practices debated at conferences like RubyConf, Agile Conference, and XP Conference. Early development occurred in the Ruby ecosystem and later expanded with a Java rewrite to support enterprise adoption, driven by contributors from organizations such as ThoughtWorks, Pivotal, and SmartBear. Over time stewardship moved through community governance, commercial sponsorship, and a formal company, with releases aligning to changes in Gherkin syntax, Cucumber Expressions, and interoperability with Behavior Driven Development tools.

Features and Architecture

Cucumber's architecture centers on a parser for Gherkin feature files, a runner that matches steps to step definitions, and formatters for output. Key features include: - Gherkin feature files with keywords like Feature, Scenario, Given, When, Then, And, But, and Scenario Outline, facilitating readable specifications for Product Owner and Business Analyst stakeholders. - Step definition matching using regular expressions or Cucumber Expressions, supporting parameter types and data tables, enabling integration with Selenium or Appium for UI automation and with Mockito or WireMock for service stubbing. - Hooks and tags that integrate with JUnit, RSpec, TestNG and allow selective execution in CI pipelines managed by Jenkins, Bamboo, or GitHub Actions. - Reporting and plugins for HTML, JSON, and JUnit-style outputs consumed by Allure, SonarQube, and enterprise dashboards.

Usage and Workflow

Typical workflow begins with stakeholders writing executable specifications in Gherkin feature files stored in version control systems such as Git, reviewed via pull requests in GitHub, GitLab, or Bitbucket. Developers implement step definitions in supported languages, linking steps to automation libraries like Capybara, Selenium, or Puppeteer. Test runs occur locally, on CI agents, or within containerized environments orchestrated by Docker, Kubernetes, or OpenShift; failures surface in issue trackers like Jira or YouTrack for triage. The living documentation produced by Cucumber feature files supports product backlog grooming and acceptance criteria validation in Sprint planning and release retrospectives.

Implementations and Language Support

Multiple implementations exist to support diverse ecosystems: the original Ruby implementation, a Java backend for JVM languages, a JavaScript implementation for Node.js, and community ports to .NET and Go. Libraries and adapters enable integration with frameworks such as RSpec, JUnit, TestNG, NUnit, Mocha, and Jest, and with build tools like Maven, Gradle, npm, and Yarn. Internationalization features allow Gherkin keywords in many human languages, broadening adoption across organizations headquartered in United States, United Kingdom, India, Germany, Australia, and Canada.

Adoption and Industry Impact

Cucumber influenced test automation and requirements practices at companies like ThoughtWorks, Google, Spotify, IBM, Microsoft, and startups adopting Agile methodologies. It contributed to an ecosystem of training, consultancy, and conference tracks at Agile Conference, STAREAST, and QCon. Academic and industry literature cites Cucumber in case studies on collaboration between Product Owner and development teams, and it shaped best practices for living documentation incorporated into DevOps toolchains and Continuous delivery pipelines.

Criticism and Limitations

Critics point to verbosity, maintenance overhead, and the risk of creating fragile mappings between Gherkin steps and implementation, leading to duplication and brittle tests in large suites—a concern raised in discussions at Stack Overflow, Software Engineering Stack Exchange, and blog posts by practitioners from ThoughtWorks and Martin Fowler. Organizations have reported challenges integrating Cucumber with microservice architectures and feature-flag workflows used by Netflix and Amazon. Alternatives and complementary approaches include specification and test frameworks like Robot Framework, pytest, and domain-specific testing tools tailored for RESTful APIs and contract testing with Pact.

Category:Behavior-driven development