Add code coverage docs when using Jest #295
Merged
Conversation
This file contains hidden or 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
This patch adds documentation detailing how to set up code coverage when using vue-test-utils with Jest. Fixes #165
eddyerburgh
reviewed
Dec 26, 2017
| ``` | ||
|
|
||
| Further documentation can be found in the [Jest configuration documentation](https://facebook.github.io/jest/docs/en/configuration.html#collectcoverage-boolean), where you can find options for coverage thresholds, target output directories, etc. | ||
|
|
There was a problem hiding this comment.
Can you add a note that mapCoverage should be set to true for coverage to be accurate
eddyerburgh
approved these changes
Dec 26, 2017
|
Thanks 🙂 |
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.
This patch adds documentation detailing how to set up code coverage when
using vue-test-utils with Jest. Also alters the header values so that sections
aren't all nested under the babel section when using screen readers etc.
Fixes #165