Don't list setups in Verify(...) error message
#779
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
Unlike `mock.Verify()` and `mock.VerifyAll()`, which look at a mock's setups, `mock.Verify(m => ...)` has absolutely no relation to setups. Listing configured setups in that method's error message can only mis- lead users into thinking otherwise. This commit removes setup information from these error messages. (The list of performed invocations is of course preserved.)
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.
Unlike
mock.Verify()andmock.VerifyAll(), which look at a mock's setups,mock.Verify(m => ...)has absolutely no relation to setups. Listing configured setups in that method's error message can only mislead users into thinking otherwise.This commit removes setup information from these error messages. (The list of performed invocations is of course preserved.)