Code coverage on Atom package specs


#1

Has anyone had any luck with running code coverage on their Atom package specs (apm test)?

I have tried with using a combination of istanbul plus coffee-coverage and wallabyjs without much luck.

The problem seems to be that when running apm test from the command line or Run Package Specs from inside Atom, it sets up a bunch of NODE_ENV include paths and window injections (this combination of NodeJS and chromium that Electron creates), which the different coverage tools doesn’t understand.


How can I find the code coverage of atom tests?
#2

There is this previous post on the idea of code coverage:

I didn’t try the technique, but it claims to work.