Better stack traces for exceptions in async tests #375

tomdale opened this Issue Dec 17, 2012 · 2 comments


None yet
2 participants

tomdale commented Dec 17, 2012

Currently, if an exception happens after stop() was called in a test (but before start()), QUnit is smart enough to associate the error with the test.

However, the output associated with the test does not provide file/line of the test itself.


jzaefferer commented Dec 18, 2012

How do you make an async test fail with an exception and still see the output? Usually the test runner hangs in that case, as start() doesn't get called anywhere.


jzaefferer commented Feb 13, 2014

Closing, since I can't reproduce the issue (see comment above).

jzaefferer closed this Feb 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment