[Core] Running empty Pickles should yield the result undefined. #1274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Running empty Pickles should yield the result undefined.
Details
Gherkin v5 does create empty Pickles for Scenarios with no steps. Running these empty Pickles should yield the result undefined, and no test steps should be executed.
Motivation and Context
See cucumber/cucumber#249 and cucumber/cucumber-ruby-core#144 (comment) for background
How Has This Been Tested?
The automated test suite has been updated to verify this behavior.
I have also manually/locally added an empty scenario to the Java calculator example to check that it indeed yielded an undefined scenario in the summary count.
Types of changes
Checklist: