-
Notifications
You must be signed in to change notification settings - Fork 11
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
Default setup reports no coverage #2
Comments
I'm not sure if I understand the issue. Are you pointing that with istanbul you get only 16.67% of coverage on the file while coverify reports 99,76%? If so, I would suggest you to first exclude the test file and all the modules that you are not testing ( About making this the default option I'm not that convinced. In my use case I have a node_module folder checked-in in my project where I define my modules, in order to avoid What do you think? EDIT: I corrected the glob patter for excluding the tests and node_modules |
I understand the statistics like it's giving me the coverage from parsing the file, but not from running the tests. The coverage stats from coverify suggest that the actual coverage is close to 100%. This looks like a bug to me. Regarding defaults: It lists exactly the files I want it to check. So there is nothing to exclude for me. |
I found the bug, great catch. The I just published v2.1.0, it also allows you to define multiple |
Now it works as expected. Thanks 👍 |
Cool. Do you mind linking this repo from the mochify README file?
|
Make it a pull request ;-) |
I'm using a simple default setup to check code coverage with these results:
Although this project has 99.76% coverage reported by coverify:
The text was updated successfully, but these errors were encountered: