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
Hi.
In our project we have 1k+ scenarios and thus rely heavily on the "Rule" keyword to group our scenarios within feature files. Currently, jest-cucumber squashes all scenarios of all rules within a feature into a flat list. This way it is not possible to have scenarios with the same title in different rule sections of one feature. Furthermore, since rules provide additional information, it would be nice if each rule and its scenarios were mapped to a separate "describe" section in jest. This way you could even see the rules in the jest output :)
The text was updated successfully, but these errors were encountered:
I've created #121 which adds this behavior to the library. In order to not introduce any breaking changes, I added a new option collapseRules which is true by default. If set to false you can use defineRuleBasedFeature() or autoBindStepsWithRules() to implement scenario steps and have each rule section mapped to different describe sections in jest.
It would be really nice if you could have a look at it and consider it for merging :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi.
In our project we have 1k+ scenarios and thus rely heavily on the "Rule" keyword to group our scenarios within feature files. Currently, jest-cucumber squashes all scenarios of all rules within a feature into a flat list. This way it is not possible to have scenarios with the same title in different rule sections of one feature. Furthermore, since rules provide additional information, it would be nice if each rule and its scenarios were mapped to a separate "describe" section in jest. This way you could even see the rules in the jest output :)
The text was updated successfully, but these errors were encountered: