Expose Mock.Setups, part 4: Mock, fluent setup & inner mock discovery
#989
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
...to get at a setup that more closely matches the original "fluent" setup expression that one would find in user code. The term "fluent" may be slightly inaccurate here: "fluent" usually applies in cases where a method returns the *same* instance for method chaining. While fluent setup expressions do feature method chaining, each method typically acts on a *different* mock object. Let's use that term nevertheless, since it's the one historically used inside Moq's code base and documentation.
stakx
commented
Apr 2, 2020
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 #987.)
This adds one new property and two new methods to
ISetup:Mock Mock { get; }to find the mock to which a setup belongs;bool? ReturnsMock(out Mock innerMock)to get at a setup's inner mock (e.g. when doing recursive verification);bool IsPartOfFluentSetup(out IFluentSetup fluentSetup)to get at the original "fluent" setup expression for those setups that have been split apart into many setups on several mocks.This will very likely conclude this series of PRs.