Displaying 2 results from an estimated 2 matches for "lcov_out".
2020 May 04
2
[EXTERNAL] How to get branch coverage by using 'source-based code coverage'
...quot;hello4"
./simple "hello5"
./simple "hello6"
./simple "hello7"
./simple "hello8"
lcov --rc lcov_branch_coverage=1 --capture --directory . --output-file
simple.lcov.info
genhtml simple.lcov.info --function-coverage --branch-coverage
--output-directory lcov_out/
gcov -b -c simple.gcno
Both gcov and lcov will give a 100% branch coverage report:
[image: cov1.png] [image: cov2.png]
My questions:
- What's the "*official*" evaluation formula on branch coverage?
Sorry I can't find any compelling documents to describe the...
2020 May 03
2
[EXTERNAL] How to get branch coverage by using 'source-based code coverage'
Hi, Alan
Really very excited to receive your email and sorry to be slow replying, it
has been exceptionally busy over the last few days ;(
Your explanation made the problem clear to me. So gcov branch coverage
should be called condition coverage and clang region coverage
is branch coverage in fact(also known as *decision/C1*), right?
And llvm/clang will support all the following coverage