Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feature: differentiate crashes from verification errors #15

Closed
quetzalcoatl opened this issue Jun 20, 2012 · 1 comment
Closed

feature: differentiate crashes from verification errors #15

quetzalcoatl opened this issue Jun 20, 2012 · 1 comment
Milestone
4.1

Comments

@quetzalcoatl
Copy link
Contributor

When a verification error occurs, the library throws MockException with a proper message. It is OK, but for some corner cases, it would be nicer, if the user code that catches that exception were able to discover whether it is a real error (like mocking nonvirtual method), or just verification failure.

I suppose the best way would be to expose a subclass - VerificationError : MockException to report them, but for the sake of simplicity, I've currently added a trivial MockException.IsVerificationError boolean property
@quetzalcoatl quetzalcoatl mentioned this issue Jun 20, 2012
Merged
@quetzalcoatl
Copy link
Contributor Author

duplicate issue, see #16

@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.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
4.1
Development

No branches or pull requests
1 participant
@quetzalcoatl