We should hook up code-coverage via codecov to our Jest test framework.
@bryphe I can take a look at this
@Akin909 - that would be a huge help! 馃挴
PR #1533 would be a good reference point.
A couple of things we'd need to do:
mocha, we needed a special hook to output the code coverage file. Jest might have an easier way, but this is how we hooked it for mocha:This outputs coverage date against the _built JavaScript files_.
remap-istanbul to map the coverage back to the sourcemaps - that happens here:Hope that gives you some ideas! Thanks a lot for the help with this 馃憤
A quick note this issue should be resolved once #2110 is merged, I've pointed jests coverage output dir to coverage/jest it outputs a coverage-final.json which I upload separately in the travis.yml codecov then does the magic of merging that report and the one for mocha into a single one
closed by #2210