Feature #1987
opengcov code coverage test support
20%
Description
We're using "make check" tests to verify that new changes aren't breaking smth. Those tests are not perfect but we don't have any measure as to "how much exactly" it's far from perfect. Because of that we also don't know if we're getting better or worse as time progress.
The standard way of doing this is by using gcov tool to produce code coverage analysis and lcov to generate nice report. This will require changes to ./configure step - see https://www.gnu.org/software/autoconf-archive/ax_code_coverage.html and corresponding additions to Makefiles.
Ideally this should be integrated with CI to see long-term trends similar to the way amount of warnings is displayed.
Related issues
Updated by fixeria almost 6 years ago
- Related to Feature #1716: enhance unit test coverage added
Updated by fixeria almost 6 years ago
- Has duplicate Feature #2599: automatically determine unit test coverage added
Updated by laforge over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
We just have merged https://gerrit.osmocom.org/#/c/libosmocore/+/13496/
Updated by fixeria over 4 years ago
- Status changed from Resolved to New
- % Done changed from 100 to 20
We just have merged https://gerrit.osmocom.org/#/c/libosmocore/+/13496/.
... so libosmocore has got the code coverage support, but not the other projects. IIUC, we should now be able to use the OSMO_AC_CODE_COVERAGE and CODE_COVERAGE_RULES macros from libosmocore (as we already do with RELMAKE).