Support Cucumber Expressions, ref #1002

[aslakhellesoy]

Summary

Support for Cucumber Expressions.

• Basic support
• Deprecate Transform (but try to make it work with current API)
• Add API for defining custom parameter types
• Print snippets as Cucumber Expressions
• Print alternative expressions above snippets

Because the Cucumber Expressions library can generate multiple expressions for an undefined step,
snippets contain all of them, with all but one commented out:

Given("I have {float} {cucumis} in my belly") do |float, cucumis|
# Given("I have {float} {veg} in my belly") do |float, veg|
  pending # Write code here that turns the phrase above into concrete actions
end

Checklist:

• I've added tests for my code
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[aslakhellesoy]

I think this is pretty much done, apart from making a new release of Cucumber Expressions. I'm really excited about putting this in the next release.

Any reservations/objections/questions?

[aslakhellesoy]

I've released cucumber-expressions 4.0.3. This can be merged to master now. Any objections or questions?

[aslakhellesoy]

Hi @aslakhellesoy,

Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾

In return for we ask you to:

• ✅ Please continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
• 💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
• 💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
• ℹ️ Don't feel obliged to help, just do what you can if you have the time and the energy.
• 🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

[aslakhellesoy]

Wow thanks @aslakhellesoy!

[maxmeyer]

@aslakhellesoy So what's left on aruba's side is add the cucumber expression steps as well correct?

[aslakhellesoy]

@maxmeyer you mean translate, not add? If you have two or more expressions matching the same text, you'll get ambiguous errors.

[maxmeyer]

@aslakhellesoy Ah ok. Was not sure, if this would make a difference. So one can only have either regex or expression step because the expression is translated into regex by the extension?

[aslakhellesoy]

That's right. No need to translate the old regexps, but it might still make sense because it might make the step definitions more self-documenting. Here is the commit where it happened in Cucumber itself: 92208f6

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.