Unordered expectations #20
Merged
Conversation
This file contains 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
| expect(message).to(equal("Expectation <(_, 3)> not matched")) | ||
| } | ||
| expect(failureMessageSent).to(beTrue()) |
There was a problem hiding this comment.
I've added these to make sure that a failure message is sent. Otherwise this test would pass even though we did not get a failure message.
felixvisee
force-pushed
the
unordered_expectations
branch
from
bea789e to
3e8039d
Compare
Merged
|
👍 |
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.
This pull request changes the verification behavior so that the order of expectations and invocations does not matter.
I've also updated Nimble to
1.0.0.Closes #19