Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade jest-preset-angular version to the latest
See original GitHub issueDescribe the bug
When running test coverage any import into a constructor (and some other things) show a false “uncovered branch” where there is no branch.
This is a long standing issue with istanbul that I believe was finally resolved.
According to this issue https://github.com/kulshekhar/ts-jest/issues/818 on ts-jest this can be resolved by simply upgrading jest-preset-angular to 7.0.0-alpha.1 instead of the current ^6.0.0
To Reproduce Steps to reproduce the behavior:
- Run tests
- See inaccurate branch coverage
Expected behavior
branch coverage should be accurate
Screenshots
(I can’t get the tooltip in the screenshot, but it says “branch not covered”)
Builder:
- The name of the builder:
@angular-builders/jest - The version of the builder:
^7.1.2
Libraries
angular-devkit/build-angular:^0.10.7
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m not sure it would be smart to add a dependency on alpha version. Let’s wait at least until RC is released and then I’ll update. If it’s a deal breaker, I can create an alpha version of
jest builderthat depends on alpha version ofjest-preset-angular.There is one pref fixing PR upcoming: kulshekhar/ts-jest#940