Istanbul ignore comments
See original GitHub issueWhen using vue-jest as transformer for .vue files istanbul ignore comments like /* istanbul ignore next*/
doesn’t take effect on coverage.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
istanbul/ignoring-code-for-coverage.md at master - GitHub
Coverage can be explicitly skipped using comments. · A coverage skip hint looks like /* istanbul ignore <word>[non-word] [optional-docs] */ · For if...
Read more >Istanbul code coverage : how to ignore such lines?
when performing code coverage , all my .catch() statements are uncovered, is there a way to specify /* istanbul ignore next */ somewhere...
Read more >Istanbul Ignore Syntax for Jest Code Coverage
Ignore a Method in a Class ... The comment must be on or above the line defining the method so it is not...
Read more >Sonar doesn't respect istanbul ignore comments - SonarCloud
The only option today is to duplicate the “istanbul” information to the property sonar.coverage.exclusions by listing all the files you expect ...
Read more >Istanbul | Best of JS
Parsing Hints (Ignoring Lines) · /* istanbul ignore if */ : ignore the next if statement. · /* istanbul ignore else */ :...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in v4, which I will release as a beta later today
Found out that if I use
babel-plugin-istanbul
(https://github.com/istanbuljs/babel-plugin-istanbul) and configure it into .babelrc the ignore isntructions works.However it returns error in some .js files - https://github.com/istanbuljs/istanbuljs/issues/73. This issue points that the error is caused by double instrumentation.
Maybe this is useful information for you @eddyerburgh .