-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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: Jest eats exceptions in native DOM events and report tests as green #4400
Comments
I made some changes to run the code in the repl and it is failing for me: |
@rknell The bad example I made is trying to demonstrate issue where exceptions are not caught when they occur off the main thread. |
Can confirm it happens, and it's both on Jest and JSDOM side. The error is logged to the console in newer version (tested on v11 |
+1, I'm seeing similar problems. I ran into this when I discovered that Jest's context was unable to create an instance of a |
@timrourke Did you find a solution to the DragEvent DataTransfer issue? |
This looked to be fixed in Jest 22, @Havunen can you please test again? The logging is quite atrocious, but it at least fails.
|
Yeah thanks guys. This is now working as expected! 👍 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hey.
There seems to be bug in Jest when used with JSDom. Errors are not caught during test runs. This can be very dangerous as tests are reported as green even though they failed. I created simple REPL to reproduce the issue.
https://repl.it/K9ij
It seems like this issue is inherited from JSDOM, but as Jest is test runner this should not happen.
The text was updated successfully, but these errors were encountered: