Christopher Hiller
                                            Christopher Hiller
                                        
                                    something like this, but try to avoid adding node-specific stuff to the default exports. this doesnβt seem applicable to the browser
We need to know exactly where this information is supposed to be printed by a reporter, and which reporters print it, or don't. Let's put the brakes on rushing to...
@twitchard For timeouts: Can this problem not be solved by making your suites and test names more unique? The spec reporter will print the timeout message directly after the suite...
the example is a little confusing due to the naming of the tests
anyway, I don't really see how it's possible to show the originating test without: - creating errors eagerly, which is a non-starter (#3119 again; be sure to understand why), or...
@vkarpov15 No, the stack trace is not going to be feasible. It would be one way of getting at the filename & line number. The *line number* is *also* not...
That being said, the groundwork for such a thing could open things up for Mocha to be extra helpful in tracking down problems... it's something I would want to investigate...
relevant: #3223
Agree it would probably not be a great idea to make this the default behavior. @mbeerta-factset Are there any workarounds at present time?
@rolfl, can you give this code a try?