search

cucumber / compatibility-kit

Platform-agnostic set of acceptance tests for validating cucumber implementations
https://cucumber.io/
MIT License
1 stars 3 forks source link

Create unused step definitions #110

Open mpkorstanje opened 4 weeks ago

mpkorstanje commented 4 weeks ago

🤔 What's the problem you're trying to solve?

It is not clear if an implementation should emit all step definitions, or only those used by a feature. It seems reasonable to me that all step definitions, used and unused are included. Formatters can then discard the data they do not need.

✨ What's your proposed solution?

Add a testcase with 1 used and 1 unused step definition. The resulting output should contain both.

⛏ Have you considered any alternatives or workarounds?

No response

📚 Any additional context?

No response

luke-hill commented 3 weeks ago

We would need to document in the feature body that 2 step definitions should exist - one that is written and parsed as (a la Given('foo')), and the other that should be written but not in the single scenario (a la Given('bar'))