Skip to content
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

Test-code-coverage and Codecov.io #51

Open
zbeekman opened this issue Dec 10, 2018 · 2 comments
Open

Test-code-coverage and Codecov.io #51

zbeekman opened this issue Dec 10, 2018 · 2 comments

Comments

@zbeekman
Copy link
Contributor

Hi @robnagler and @dtabell, in an effort to ensure correctness as modifications and refactorings move forward, it would be nice to have some code-coverage data to help get a sense of which portions of the code-base are actually executed. On my automate-profiling branch I have setup a code-coverage build configuration.

Would it be possible to enable Codecov.io for zgoubi?

That way, we could update code-coverage metrics during CI testing.

To build with code-coverage support, add the -DCMAKE_BUILD_TYPE:STRING=CodeCoverage flag to the CMake configuration line (or selecting it from the drop down UI in ccmake or cmake-gui) will build zgoubi with code coverage enabled. I'm still looking into the best way to process the coverage output with GCov inside the docker environment in use for CI testing.

What do you think?

Thanks,
Zaak

@robnagler
Copy link
Member

@dtabell I defer to you.

@dtabell
Copy link
Contributor

dtabell commented Dec 12, 2018

Hi @zbeekman. Would be very nice to have some idea of how much of the code is actually getting tested, so sounds to me like a good thing to do. Is there any downside?

Dan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants