Hi @mpaladin,
Thank You for the response.
Unfortunately gcov must be run inside each source folder.
I helped myself with Using Relative Paths With GCOV Sensor
and I got to the point where *.gcov are stored with test .cpp files and .gcno and .gcda files(last two are actually not important), and I set sonar.cfamily.gcov.reportsPath=. and sonar.projectBaseDir=${WORKSPACE}/gw
With this some coverage shows up, but seems like not all files are being scanned with proper coverage, one example:
gw/src/res/v/v/xxx.cc (Coverage 0%) - actually real coverage for this file is 85%
gw/src/res/v/v/tests/test-xxx.cpp (Coverage 77.5%) - test code for xxx.c
gw/src/i/n/v.cc (Coverage 43.9%) - actually real coverage for this file is 85%
gw/src/i/n/tests/test-v.cpp (Coverage 83.3%) test code for v.cc
Why there is a difference between xxx and v, while in reality they both have +85% coverage
gw/src/a/c/v/mapp.c (Coverage 13.6%) - tested file
gw/src/a/v/tests/mapp_test.cpp (Coverage 32.8%) test code for mapp.c
xxx.cc and v.cc (and dozen of others files) are relatively new files with more than 85% coverage with their tests being test-xxx.cpp and test-v.cpp, I don’t know why some files gets no coverage at all like xxx.cc while they have the same directory recess, like v.cc which gets coverage. Most coverage I have is from test files itself, not the tested files. I’d like to have it like in “v” files.