cucumber

Run all features

$ cucumber

$ cucumber [features/login.feature]

$ cucumber [features/login.feature]:[10]

$ cucumber --tags @[smoke]

$ cucumber --tags "not @[wip]"

$ cucumber --format html --out [report.html]

$ cucumber --dry-run

cucumber [options] [files|dirs]

cucumber runs Behavior-Driven Development (BDD) tests written in Gherkin, a human-readable language for describing software behavior. It connects plain-language scenarios to executable step definitions.
Features describe behavior in Given/When/Then format that both developers and stakeholders can understand. Step definitions in Ruby (or other languages) implement the actual test logic.

-t, --tags expr

Run scenarios matching tag expression.

Output format (pretty, progress, html, json).

Write output to file.

Require files before execution.

Check syntax without running.

Fail on undefined or pending steps.

Retry failing scenarios n times.

Use named profile from cucumber.yml.

Run order (defined, random).

Step definitions must match scenario steps exactly. Shared state between steps can cause flaky tests. Gherkin syntax errors stop execution. Slow for large test suites.

Cucumber was created by Aslak Hellesoy in 2008, inspired by RSpec and JBehave. It popularized BDD by enabling executable specifications in plain language. Originally Ruby-based, implementations now exist for Java, JavaScript, and many other languages.

rspec(1), behave(1), jest(1), pytest(1)