-
Notifications
You must be signed in to change notification settings - Fork 6
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
Question - Can you filter test files from the coverage report? #14
Comments
This usecase has not been retested since the babel integration so I don't know if that's a bug or not! I will look that asap |
Investigated further and found a few things. The short answer is it does not filter. The long answer, found other issues: In my project we keep meteor testing packages our of .meteor/packages and .meteor/versions. We add meteortesting:[email protected] when we run the tests. That package incorrectly installs bad versions of lmieulet:meteor-coverage and meteortesting:mocha-core that do not exclude the results. If you delete the following lines:
And run rm -fR .coverage
meteor npm run test:coverage You will see the wrong versions are being installed.
lmieulet:meteor-coverage ends up as 1.1.4 instead of 3.1.1 The workaround is to explicitly install these versions before running coverage report. |
So I forked this project and stripped from .meteor/versions and .meteor/packages
I add meteortesting:mocha via Fork of the example app is at https://github.com/geoffcorey/meteor-coverage-app-exemple/commit/0f1574c8bcd4a5d17a5987b92be5078a59d16520 I think at the very least the basic instructions for adding code coverage need to be updated and/or meteortesting:mocha should be installing the same versions as your example app. Thoughts?
|
Sorry for the late answer. I can confirm your issue on my side. The issue starts here:
Why the hell installing And if you execute the command I give in the readme However, your original issue is confirmed as tests files are still in the coverage report. Need to look at it, but maybe all the system that prevents tests file to be in the report have been ignored with the new babel feature, I don't know yet |
Reading meteor-mocha https://github.com/serut/meteor-coverage#meteor-ignored-folders-and-files is would have assumed the test files would be excluded from the report however I see your bare-exemple app is still showing the test files in the html report. I tried modifying .coverage.json and see it does not have any affect. Am I missing something? Should I be trying to exclude from the report via istanbul plugin in babel config or .istanbul.yml file instead.
.coverage.json
The text was updated successfully, but these errors were encountered: