config settings to generate html cover coverage reports locally #552
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -22,6 +22,9 @@ settings = { | |||
| presets: ['es2015'] | |||
| }), | |||
| istanbul({ | |||
| instrumenterConfig: { | |||
There was a problem hiding this comment.
Would you mind adding a comment linking to this ?
|
👍 |
|
Showing the coverage increases the coverage. There's something deeply philosophical about that. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
some karma config changes so that HTML code coverage reports are generated when we run
npm run test-local.HTML reports would provide more immediate feedback than using coveralls.io