Skip to content

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

Closed
sindresorhus opened this issue May 20, 2015 · 2 comments
Closed

Error context #22

sindresorhus opened this issue May 20, 2015 · 2 comments
Labels
enhancement new functionality

Comments

@sindresorhus
Copy link
Member

Tape has this nice output on errors:

at: Test.<anonymous> (/Users/sindresorhus/dev/hypot/test.js:9:4)

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

@kevva
Copy link
Contributor

kevva commented May 20, 2015

Yeah, if you look at the stack we produce we could mostly (don't know if that's the case in throws and doesNotThrow) just remove the first line in it to get the correct line and file.

But yeah, we could go the tape way too.

@sindresorhus sindresorhus added the enhancement new functionality label Aug 27, 2015
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
@mdibaiee
Copy link

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
Labels
enhancement new functionality
Projects
None yet
Development

No branches or pull requests

3 participants