You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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'))
luke-hill
changed the title
Create unused step definitions
Create "unused step definitions" feature
Jan 29, 2025
🤔 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
The text was updated successfully, but these errors were encountered: