-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Error context #22
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
Labels
enhancement
new functionality
Comments
Yeah, if you look at the stack we produce we could mostly (don't know if that's the case in But yeah, we could go the |
mdibaiee
pushed a commit
to mdibaiee/ava
that referenced
this issue
Aug 29, 2015
Fix "Assertion count does not match planned" error's stack trace not showing
Hey, I'd like to work on this. I opened a pull-request and I want your feedback on that. #29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tape has this nice output on errors:
Currently we output the full stack trace or none.
This might be something
claim
should handle.https://github.com/substack/tape/blob/ccfcf4f76581abc3842163dfe065198764247c85/lib/test.js#L207
The text was updated successfully, but these errors were encountered: