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.

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

Improve failure message #632

Open
floehopper opened this issue Nov 18, 2023 · 0 comments
Open

Improve failure message #632

floehopper opened this issue Nov 18, 2023 · 0 comments

Comments

@floehopper
Copy link
Member

floehopper commented Nov 18, 2023

While working on #60, it struck me that the failure message could include details of each invocation and which expectation it matched. While I think this would make it easier to address #60, I think it might have a lot of other advantages. We could display each invocation including the actual arguments together with either the matched expectation or (for unexpected invocations) a list of expectations that might have matched if it weren't for certain constraints.

Looks like there might be some overlap with #177, #178 & #179 which all came out of #167 and might be a good way to split this up...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant