v2.1.1

• 🐛 Fix normalisation of feature files. #14

Full Changelog: v2.1.0...v2.1.1

v2.1.0

• ✨ Added cucumber::run() function to allow running Cucumber tests alongside testthat tests.
• 🐛 Don't normalize feature files text within docstrings or tables.
• 🐛 Don't include docstrings and tables when validating feature files.

v2.0.0

See the migration guide.

• ✨ You can now run specifications directly with cucumber::test() function.

v1.2.1

• 🐛 Fix hook registering that previously could only register one hook.

Full Changelog: v1.2.0...v1.2.1

v1.2.0

What's Changed

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

Full Changelog: v1.1.0...v1.2.0

v1.1.0

• ✨ Added scenario before and after hooks.
• 📝 Added Behavior-Driven Development vignette.
• 🐛 Fix parsing error when there is a commented-out scenario after a step with a table.

1.0.4

• Added test_interactive parameter to cucumber::test. It allows you to interactively select which feature files to run. It can be useful to get quicker feedback when developing new features.

v1.0.2

• 🔧 CRAN fixes

v1.0.1

• ✨ Changed how {string} parameter is matched. It now matches on text in quotes. A step Given I have a {string} will match on Given 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 like Given I have a {word} will match on Given 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} and Given I have a {string} it will match on Given 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_type function docs.
• 📝 Added an example with snapshot test.

v1.0.0

First release