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
Let the result types affected the the strict settings be controlled individually, so only a subset of the can be set to be handled strict.
Details
Add the options
--[no-]strict-undefined
,--[no-]strict-pending
, and--[no-]strict-flaky
,so each of the result type affected by the strict settings be controlled individually.
The
--[no-]strict
option is equivalent to--[no-]strict-undefined --[no-]strict-pending --[no-]strict-flaky
.Also make sure that it is possible from the command line to adjust the strict setting from a profile, for instance:
Given that a profile includes the
--strict
optionWhen using
--no-strict-flaky
on the command lineThen only
undefined
andpending
will be handled strictDepends on cucumber/cucumber-ruby-core#143.
Motivation and Context
Fixes #1160.
How Has This Been Tested?
The automated test suite has been updated to verify this behaviour.
Types of changes
Checklist:
--help
option will describe the new options).