Bug: typeCoverage config not working
See original GitHub issueDescribe the bug
In the provided example, I am expecting the tool to fail since the expected actual coverage is 92%
, and my provided minimum is 99%
. This works when using the CLI option, but not when using the typeCoverage
property in package.json
.
Provided config:
"typeCoverage": {
"atLeast": 99
},
CLI output when using typeCoverage
(wrong behavior):
CLI output when using --threshold
option (expected behavior):
As a side note, noticed the cache
option to generate .ts-coverage
does not seem to work either, I suspect it may be related.
To Reproduce See: https://codesandbox.io/s/crazy-sound-ujkcu
You can export the CodeSandbox as a zip and run locally after yarn install
.
Expected behaviour
Using typeCoverage
should have parity with typescript-coverage-report
CLI options.
Screenshots N/A
Environment
- Tool version: 0.1.1
- OS: MacOS 10.15.3
- Node version: 12 LTS
- Browser (if applicable): [e.g. chrome, safari]
Additional context N/A
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (12 by maintainers)
@danvk I just released this as part of v0.3.0
+1 to this! I added an
ignoreUnread
option totype-coverage
recently and would like to use it with typescript-coverage-report.