Conversation
Member
Author
|
The error message is pretty terrible. We will see it only when there is no default behavior, so there must be at least 1 paramtrized mock. I tried to show what we evaluated in order to reach that point where no filter matched. but the wording needs to be better, and well as the formatting of the invoked filters I think. But then we should be able to re-use similar thing for Should -Invoke to show the history of execution, when failing should Invoke. To show the performed invocations. |
This file contains hidden or 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
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.
PR Summary
Removes fallback to the mocked command. And replaces it with error message .
Fix #2178