-
Notifications
You must be signed in to change notification settings - Fork 63
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
add code coverage to nightly system #60
Comments
https://cmake.org/Wiki/CTest/Coverage has some discussion of this, but was last updated in 2014 and doesn't seem tremendously straightforward. https://github.com/bilke/cmake-modules/blob/master/CodeCoverage.cmake seems like it might be a good module to use to include coverage analysis. |
thanks, @TobinW. looking at CodeCoverage.cmake, one issue I have is that coverage is done on a per-test basis, and it would probably be better to use gcov's ability to aggregate data from all test runs into a single coverage report. In relation to #58, I wonder if we should create a coverage report for |
This functionality is pulled over from my implementation in tobinw/biotissue. Valgrind is used to do memory checking, and gcov is used for coverage. closes SCOREC#60
No description provided.
The text was updated successfully, but these errors were encountered: