pivotal/jasmine — pull request #468 by GerHobbelt (2013-11-23 00:31:50+00:00)
Title: make sure the stacktrace printed by Jasmine on failing to pass an `expect(f)` shows the faulty user code

make sure the stacktrace printed by Jasmine on failing to pass an `expect(f).toThrow()` or `expect(f).not.toThrow()` is the exception stack that shows the first USER CODE exception whenever possible.

Previously, these tests would create a default stackdump (created by stack() inside the Jasmine stack itself) which is useless when you need to track down the origin of the unexpected(!) exception which can occur anywhere in the user test code.

Note: jasmine grunt test task again passes all tests with this edit.