Only log console messages if there's a spec in progress.

[mathie]

Frameworks that logged to the console during initialization (eg EmberJS) were causing an error because logs[-1] was undefined. For bonus points, Ember helpfully swallowed this error in development and carried on, meaning that all the tests would mysteriously fail instead...

It might be useful to start logging these 'global' log messages too and communicating them back to the runner, but at least this gets my tests running again. :)

[rud]

This discards the startup messages if I understand it correct. Would it be possible to capture them instead and emit them when possible?

[swistak]

Yes the problem is -1 is used to log "global errors", and since recently terrors ARE comunicated back to user. Change was introduced by me here:

swistak@e431dcc

Your change would break that functionality.

[swistak]

Better solution would be probably to change:

logs = {}

to

logs = {"-1": []}

which should fix error with logs while not impairing global reporting functionality.

[netzpirat]

I agree with @swistak, initialize the "global" logs array would be the best solution to fix the issue and not break global log reporting.

[swistak]

Sorry It's my fault should have written spec to test that functionality

[netzpirat]

@mathie Can you please verify that the change solves your issue, so I can release a new version?

[mathie]

@netzpirat That's fixed it, thanks!

[netzpirat]

Version 1.15.1 is out that contains this fix. Thank you all!