Open tandrewnichols opened 10 years ago
:+1: I think we need to unrecursify this.
On Fri, Feb 28, 2014 at 5:04 PM, Andrew Nichols notifications@github.com wrote:
Because it's async, every new test adds a level to the stack, so if test 57 fails, you see A LOT of "Waterfall.flow" in the stack trace. With multiple errors, it becomes really hard to find the actual error.
Reply to this email directly or view it on GitHub: https://github.com/searls/jasmine-given/issues/26
Perhaps. There's also this, which could make handling long stack traces easier: https://github.com/felixge/node-stack-trace
99% of given use isn't on node though
On Sun, Mar 9, 2014 at 2:41 PM, Andrew Nichols notifications@github.com wrote:
Perhaps. There's also this, which could make handling long stack traces easier: https://github.com/felixge/node-stack-trace
Reply to this email directly or view it on GitHub: https://github.com/searls/jasmine-given/issues/26#issuecomment-37134537
Ah, I see. Unrecursify it is then.
Because it's async, every new test adds a level to the stack, so if test 57 fails, you see A LOT of "Waterfall.flow" in the stack trace. With multiple errors, it becomes really hard to find the actual error.