expect(0) error doesn't have useful stack trace

[wycats]

When a test has no assertions, QUnit throws "Expected at least one assertion, but none were run - call expect(0) to accept zero assertions".

Because this error is inside QUnit code and not test code, the exception information is not very useful. At first glance, it seems like it may be impossible to provide better information, but I'm opening this ticket to try to brainstorm a better solution.

[jzaefferer]

I see no way to add a useful stack trace in this case. In af27eae I actually remove the useless trace for unmatched expect and expect(0), so that's at least better then pointing to some line inside qunit.js.

[jzaefferer]

Try to save stacktraces for test() or module() calls when they are made (or rather the one line). When a related test fails where nothing is accessible, use that stored stack.

[jzaefferer]

Fixed