Coverage of C++ code
Created by: paulromano
We currently obtain coverage of Python code during testing, which is then reported on coveralls. So, with respect to Python, we at least know what is not being covered. For C++ code, we actually are not collecting/reporting coverage numbers at all right now. Getting coverage will look something like the following:
- Add a CMake option (rather fix the existing option) to throw coverage flags on. Looks like
--coverageis all that's needed.
- When OpenMC is run,
.gcdafiles (in the build directory alongside object files) that contain coverage information
lcovto collect information from the
.gcdafiles into a single file.
- At this point there are multiple options. We might be able to report C++ coverage in a separate CI job, and coveralls parallel build webhook might take care of this appropriately? Not sure. If we can't combine with existing Python coverage, we could also use a different service (e.g., codecov) to report C++ coverage.