-
Notifications
You must be signed in to change notification settings - Fork 22
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
Figure out how to measure Python test coverage #80
Comments
@edwardhartnett |
We should also figure out a way to measure C test coverage. The gcovr utility doesn't currently measure the C portion of the library either; rather, it only does the Fortran portion. |
@jbathegit the spirit is willing, but the flesh is weak. ;-) However gcovr works equally with C code, it just needs to be pointed at the correct subdirectories... However, if you can figure this out, we will happily use it on the other projects. |
As of #249, this is now resolved for the C portion of the library. But we still need to figure out how to measure coverage for the Python portion of the library. |
Well I used to know how to do this, so I've got to figure it out again. ;-)
The text was updated successfully, but these errors were encountered: