You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the colors config is false, I've noticed various bad behaviors related to using console.log in the test code.
For both PhantomJS and Chrome (the only two browsers I tried), I see that the logged text always starts on the line after the LOG prefix, and there is no line terminator between the text and the next logged line. For example console.log('xxxxxxx') logs as:
When the colors config is false, I've noticed various bad behaviors related to using console.log in the test code.
For both PhantomJS and Chrome (the only two browsers I tried), I see that the logged text always starts on the line after the LOG prefix, and there is no line terminator between the text and the next logged line. For example console.log('xxxxxxx') logs as:
LOG: LOG
'xxxxxxx'PhantomJS 1.9.0 (Windows 7): Executed 0 of 1 SUCCESS (0 secs / 0 secs)
Further, for PhantomJS (not Chrome), if the text is less than 7 characters long, it logs nothing. For example console.log('xxxxx') logs as:
LOG: LOG
PhantomJS 1.9.0 (Windows 7): Executed 1 of 1 SUCCESS (0.37 secs / 0.035 secs)
The text was updated successfully, but these errors were encountered: