Wraps assert functions, updating stack trace of generated errors #690
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should solve #317
The stack trace of assertion errors created by supertest doesn't refer back to the point where
.expect(…)
call was made. The trick done here saves the stack of when.expect(…)
was called, and inserts that back into the.stack
of any possible assertionError
created later.Example:
I created a file name
supertest-test.js
with the following content:When running
node ./supertest-test.js
, this was the output:The content referred by
…/supertest-test.js:5:4
is exactly the call to.expect(200)
.