[Core] Add property to skip execution of tagged scenarios #2952
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.
🤔 What's changed?
Adds
cucumber.execution.skip.tags
. This will skip execution of all steps and hooks in any pickle that matches the tag expressions. This differs fromcucumber.filter.tags
which removes the matching pickle from execution altogether.Note: Conceptually Cucumber and the JUnit Platform have different definitions for what it means to skip test. This makes things complicated.
cucumber.execution.skip.tags
JUnit will consider the test to be aborted because from its perspective Cucumber started the execution and then skipped all steps, thus aborting the test.cucumber.filter.tags
JUnit will skip the test, never starting the execution and thus omitting it from any Cucumber reports.⚡️ What's your motivation?
Quick proof of concept for: #2951.
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
📋 Checklist: