Tests coverage

Hi coryhouse !

First I would like to thank you for this great starter project.

I recently start to develop with this and when I wanted to generate my test coverage I realized that I’ve got a coverage at 100% while I haven’t done any test.

After some researches, I found that the coverage was only applied on .spec files, so only js files with a spec file defined are registered for the coverage.

So I did this in my package.json :

"test": "mocha tools/testSetup.js \"src/app/**/*.js\" --reporter progress",
"test:cover": "babel-node node_modules/isparta/bin/isparta cover --root src --report html node_modules/mocha/bin/_mocha -- --require ./tools/testSetup.js \"src/app/**/*.js\" --reporter progress"

And now I have a full coverage on all my js files, and a correct percentage value (- which is far from 100% !).

Note : it seems that mocha is unable to load index.js and webpack-public-path.js, so I put my all app in a ‘app’ subfolder.

I hope this can be usefull to somebody 😉

[silentbobbert]

I think @kwelch has now got a test runner that works on Windows with coverage enabled 👍

[kwelch]

test:cover looks good for me on the new jest branch.

I would appreciate it, if @nibblesnbits could review with Windows 10 and let me know if the move to jest resolves that issue.

I expect it would, but prior to merging the jest branch I would love to have that confirmed