Expose Mock.Setups, part 2: Match status of setups & invocations
#985
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
stakx
commented
Mar 31, 2020
| this.SetOutParameters(invocation); | ||
|
|
||
| // update condition (important for `MockSequence`) and matchers (important for `Capture`): | ||
| this.Condition?.SetupEvaluatedSuccessfully(); |
There was a problem hiding this comment.
Interesting to note that Condition no longer needs to remain public; it is now only ever queried from within the same type.
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 is a follow-up to #984.)
This allows you...
to distinguish between unmatched setups and those that were matched by at least one invocation via the
ISetup.WasMatched { get; }boolean property; andto find out whether an invocation matched a setup (and which one) via the
IInvocation.WasMatched(out ISetup matchingSetup)method.