-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
🐛 Bug: Errors messages and stack traces from JSDOM loaded scripts are not useful #1757
Comments
@danielstjules In my test case it looks like #1767 prints out pretty much the same as the Output for #1767
|
@danielstjules I'm gonna put this on your plate 😄 |
@boneskull haha cool, will take a look this weekend |
Any updates on this? 😄 |
I am a bot that watches issues for inactivity. |
This should have been fixed in #1767. Also the issue is very old and hasn't been interacted with since 2017. Marking as closed. ✔️ But if I'm wrong and it's still an active issue, please do file a new issue using one of our new issue templates. They'll ask for the info we'd need to re-triage this. Cheers all! |
I put up a test case repo at https://github.com/mjhm/mocha_jsdom_test
As mentioned in the README the repo shows a change in handling jsdom stack traces.
The problem is that for mocha@2.2.X the handling of stack traces has changed so that stack traces of JSDOM loaded scripts are no longer useful.
In particular the report of last test using mocha@2.1.0 is
But the result for mocha@2.2.5 is not useful for tracking down the source of the error:
There are differences in the other tests as well.
jsdom
.Complete test report for mocha@2.2.5:
Complete test report for mocha@2.1.0
The text was updated successfully, but these errors were encountered: