Skip to content

mock.Verify and mock.VerifyAll leak internal MockVerificationException type #507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
stakx opened this issue Oct 24, 2017 · 0 comments
Closed
Labels
Milestone

Comments

@stakx
Copy link
Contributor

stakx commented Oct 24, 2017

That exception type is delared internal and therefore cannot be specifically caught with a dedicated catch clause. But it can be seen in the exception message when it occurs.

This type was apparently introduced as an internal mechanism to aggregate mock exceptions during a broad MockRepository.Verify or VerifyAll call. Only MockException should be thrown directly.

@stakx stakx added the bug label Oct 24, 2017
@stakx stakx added this to the v4.8.0 milestone Nov 3, 2017
@stakx stakx closed this as completed Nov 3, 2017
@devlooped devlooped locked and limited conversation to collaborators Sep 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant