-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Coverage for all files using karma and includeAllSources: true #29
Comments
We ran into the same issue. I found this issue on the karma-coverage github: karma-runner/karma-coverage#125 Unfortunately this has not been resolved yet, but one user recommended the plugin https://www.npmjs.com/package/karma-coverage-allsources - this is working for us. Give that one a try! |
I just ran into this issue as well. What is the process for getting it to work? Should someone port the |
Same issue. But with I tried to use the What would be the proper setup for Here is the
Here is the lineup of the libraries in
Here is the code snippet from
|
@joyfulelement we've added support for |
How would one use the |
@wezleytsai @joyfulelement @sontek @davidklassen there's an approach outlined here, for covering all files using Karma: For technologies other than Karma, there are various approaches to achieving coverage of untested files:
|
Hello,
I'm using a setup with karma+jasmine+babelify for testing, my directory structure looks like this:
This is the karma.conf:
I'd like to make use of includeAllSources: true option for coverageReporter but can not find a way to have instrumentation for all files in src/ dir.
The text was updated successfully, but these errors were encountered: