Alexander Mills

accomplish this by patching `process.stdout.write` and `process.stderr.write`, obviously

https://www.npmjs.com/package/js-beautify

https://chrome.google.com/webstore/developer/update

https://developer.chrome.com/extensions/manifest

or we can potentially use: ```js const fs = require('fs'); fs.access('./foobar.sh', fs.constants.X_OK, (err) => { console.log(err ? 'cannot execute' : 'can execute'); }); ```

+1 this has always sucked, good call

I have a similar question.

this was a GREAT thread...and I got it to work! I wrote up an article on how to do this: https://medium.com/@the1mills/front-end-javascript-test-coverage-with-istanbul-selenium-4b2be44e3e98 @attodorov I gave you credit for my findings :)...

I wrote up an article on how to do this: https://medium.com/@the1mills/front-end-javascript-test-coverage-with-istanbul-selenium-4b2be44e3e98

I can try to help...first this article might help: https://medium.com/@the1mills/front-end-javascript-test-coverage-with-istanbul-selenium-4b2be44e3e98 You want to use window not global, because that script is executing in the browser. Looks like I am using...