karma-runner / karma-runner/karma-coverage
Incorrect branch coverage when using implicit else post
- Dominant language
- JavaScript
- Stars
- 771
- Forks
- 242
- PR merge metrics
- No merged PRs in 30d
Description
HI I am unsure if this is the right way to report/request a update to the istanbul-reports dependency. But, it appears that the version that karma-coverage is using may be the source of some issues I can not provide any information of my current project but the issue outlined here https://github.com/istanbuljs/istanbuljs/issues/670 is exactly the same. Currently using karma-coverage 2.2.0 in our project, It looks like the problem might be fixed in the newest version of istanbul-reports 3.1.4 but I have no clue how I would go about testing this. Sorry I am a very jr dev.
Contributor guide
Research direction
Start with the linked istanbuljs issue #670 and inspect how karma-coverage 2.2.0 selects its istanbul-reports dependency. Compare that dependency with istanbul-reports 3.1.4 and reproduce the incorrect branch coverage for an implicit else post. Done means confirming whether the dependency update resolves the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100