Make strict mocks recognize that .CallBase() can set up a return value, too
#450
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
which demonstrates that a strict mock does not currently recognize that a setup such as `strictMock.SetupGet(...).CallBase()` provides a return value.
The `ExecuteCall` interception strategy shouldn't just ask `Method- CallReturn` whether it "has a return value"; make it ask whether it "provides a return value" (as per the exception message text), then implement the required check (which now also takes `CallBase` into consideration) directly in `MethodCallReturn`. Also, clean up and rewrite the `MethodCallReturn` class a little bit to make it easier to read.
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 fixes #448.