Make the satisfyAllOf and satifyAnyOf matchers fail correctly when the submatchers fail #860
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.
I found that the
satisfyAllOf
andsatisfyAnyOf
matchers wouldn't correctly fail if there was a matcher than had returned statusfail
.This changes both the
satisfyAllOf
andSatisfyAnyOf
matchers to always fail, regardless of the result of the other submatchers, if any of the submodules returns with status fail. After failure, this will still run the rest of the matchers, just to get the correct error message.The PR should summarize what was changed and why. Here are some questions to
help you if you're not sure:
Checklist - While not every PR needs it, new features should consider this list: