cucumber 2.1.1
- 🐛 Fix normalisation of feature files. #14
cucumber 2.1.0
CRAN release: 2025-05-20
- ✨ Added
cucumber::run()function to allow running Cucumber tests alongsidetestthattests. - 🐛 Don’t normalize feature files text within docstrings or tables.
- 🐛 Don’t include docstrings and tables when validating feature files.
- 🧪 Added cucumber tests in
tests/acceptance.
cucumber 2.0.0
CRAN release: 2025-04-04
See the migration guide.
- ✨ You can now run specifications directly with
cucumber::test()function.
cucumber 1.2.1
CRAN release: 2025-03-20
- 🐛 Fix hook registering that previously could only register one hook.
cucumber 1.2.0
CRAN release: 2025-02-24
- ✨ Added support for “Scenario Outline”, “Background” and “*” keywords.
- ⚠️ Keywords are not taken into account when looking for a step definition. See Gherkin steps reference.
- 🛡️ Added validation of feature files to fail early if malformed:
- Checks for consistent indentation.
- Check if a feature file has only one Feature.
- ✨
afterhook runs even if a scenario fails. This is useful for cleaning up resources even if a test fails unexpectedly. - ✨ Added option to set the indent of feature files. Useful when you use a different indent than the default 2 whitespaces. All user-facing options are documented in
?cucumber::opts. - 📝 Added “Gherkin Reference” article.
cucumber 1.1.0
CRAN release: 2024-10-14
- ✨ Added scenario
beforeandafterhooks. - 📝 Added Behavior-Driven Development vignette.
- 🐛 Fix parsing error when there is a commented-out scenario after a step with a table.
cucumber 1.0.4
CRAN release: 2024-06-29
- Added
test_interactiveparameter tocucumber::test. It allows you to interactively select which feature files to run. It can be useful to get quicker feedback when developing new features.
cucumber 1.0.3
CRAN release: 2024-06-09
- Fixed float detection with multiple leading numbers, e.g.
11.1,+11.1,-11.1.
cucumber 1.0.1
CRAN release: 2024-04-03
- ✨ Changed how
{string}parameter is matched. It now matches on text in quotes. A stepGiven I have a {string}will match onGiven I have a "foo bar". This change brings the parser closer to how the original cucumber expressions work. - ✨ Added a
{word}parameter that matches on a single word. A step likeGiven I have a {word}will match onGiven I have a foo. - 🐛 Fix handling of repeated parameters in the same step. Now if there are steps
Given I have a {string} and a {string}andGiven I have a {string}it will match onGiven I have a "foo" and a "bar"instead of throwing an error that multiple step definitions have been found. - 📝 Improved documentation of parameters in
define_parameter_typefunction docs. - 📝 Added an example with snapshot test.
