-
-
Notifications
You must be signed in to change notification settings - Fork 512
skeleton-esnext test coverage report shows compiled code, not source code. #541
Comments
There's a PR in to address this which we are evaluating as well as a number of other solutions. |
Any update on this? Same problem in webpack skeleton. |
#519 fixed it. Now it looks like this for I'm not sure how to run the coverage task on the webpack skeleton. |
In the webpack skeleton, run the tests - 'npm test' - that should generate the coverage. It is set up to only generate JSON - you can change the reporter entry in karma.conf.js to get HTML.
I see a problem that if you run it twice, some coverage report files get dumped into the src folder. These files appear to be reports on the non-transpiled source - but html image and css resource file paths are broken, so they don't display nicely. Plus, you don't want them in the src folder :-} I have stopped these files getting generated by modifying the test runner script in package.json to delete the coverage directory before running:
|
@stevies would you mind copying what you just posted to a new issue? I'm going to close this one as the initial issue has been fixed. |
From a clean skeleton repo,
gulp cover
yields coverage report like this.Is this a known issue?
The text was updated successfully, but these errors were encountered: