Run cucumber in strict mode#392
Merged
Merged
Conversation
By default, cucumber do not return an error when some step definitions are missing: it only produce an informational message with code snippet before exiting. On CI, this is "lost" and when we break a test, it may seem the CI is passing while in fact the test is just broken and not tested anymore. When running in strict mode, cucumber will exit with an error in such condition.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default, cucumber do not return an error when some step definitions are missing: it only produce an informational message with code snippet before exiting.
On CI, this is "lost" and when we break a test, it may seem the CI is passing while in fact the test is just broken and not tested anymore.
When running in strict mode, cucumber will exit with an error in such condition.