Feature #1987

gcov code coverage test support

Added by msuraev almost 4 years ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


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 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

Related to libosmocore - Feature #1716: enhance unit test coverageNew05/17/2016

Has duplicate Cellular Network Infrastructure - Feature #2599: automatically determine unit test coverageResolved10/27/2017


#1 Updated by fixeria over 2 years ago

#2 Updated by fixeria over 2 years ago

  • Has duplicate Feature #2599: automatically determine unit test coverage added

#3 Updated by laforge about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#4 Updated by fixeria about 1 year ago

  • Status changed from Resolved to New
  • % Done changed from 100 to 20

We just have merged

... 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).

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)