VerifyNoOtherCalls
: Fix bugs with Mock.Of<T>
#543
Merged
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 PR ensures that mocks created with
Mock.Of<T>
initially have no recorded invocations.Due to the way
Mock.Of<T>
is currently implemented, mocks created using this method might already have recorded invocations. This never really mattered up until now, where it can interfere withVerifyNoOtherCalls
.This solves one of two issues with the initial
VerifyNoOtherCalls
implementation, as tracked in #527 (comment).