-
-
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
Added option to allow unhandled exceptions to propagate in the browser #1659
Conversation
This results in a slight change to the behavior of --async-only: instead of failing immediately, check to see if the test returned a promise (or otherwise failed) before complaining about not having a done callback.
* commit '7657cb11d960cf2cd8407b256019b2e34dc93328': Allow --async-only to be satisfied by returning a promise
+1 |
I don't get it. Why don't we just do both? |
@boneskull now it does 👍 |
@mochajs/mocha seems like a good idea to me for minor release. if there is no disagreement I will merge this |
@amsul can you rebase on top of branch |
@boneskull done |
lgtm. |
Show string diff as a raw data, this fix issue mochajs#1241.
added tests for allowUncaught option error handler prints to dom with allowUncaught
This results in a slight change to the behavior of --async-only: instead of failing immediately, check to see if the test returned a promise (or otherwise failed) before complaining about not having a done callback.
fixed merge issues fixed merge issues fixed merge issues
@amsul I don't think you can actually change which branch you're making a PR against, so you may want to actually open a new one. I'm going to close this to make sure it doesn't get accidentally merged.
Thanks! |
Added option to allow unhandled exceptions to propagate in the browser (rel #1659)
Related to #553
This adds the
mocha.allowUncaught
method.When the method isn’t invoked, the console is empty:
When the method is invoked, the console shows the unhandled exception: