New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nyc-config-typescript: bug in code coverage #523
Comments
I have the same the same issue. Very strange. When i use @istanbuljs/nyc-config-typescript with version ^0.1.3 then i have no issue. |
probable fix is #518 |
Hello, is there any update on this issue? We are seeing the same issue (0% coverage) when we add extends to the nyc config file. Thanks in Advance. |
@Raag007 |
Hello, Results without extends.
Results with extends.
Do you know why we have to use this package and why it changes the behavior of nyc code coverage? Thanks! |
When using the
@istanbuljs/nyc-config-typescript
to extend the coverage from nyc for a typescript project written in mocha, there's a bug.If I run a test where I'm not extending from the
@istanbuljs/nyc-config-typescript
, then I get proper code coverage results through nyc. Here's an example printout (I'm setting code coverage thresholds all to 100 in my nyc configurations).My script in my package.json that I'm running:
And here's the nyc configuration I have in my package.json:
The result:
Now I remove the
extends
line:And running the same command I get:
AKA, coverage is working. What's the issue here?
The code I'm testing is from the following: https://github.com/Azure/azure-iot-sdk-node/tree/master/common/transport/mqtt
The text was updated successfully, but these errors were encountered: