Code coverage for the current build versus the build triggered previous minus last build

[ganncamp (G Ann Campbell)]

Hi,

Thanks for providing a detailed scenario. I see multiple questions here. As a best practice we try to keep it to one question per thread because otherwise it can get very tangled and difficult to know what’s answered satisfactorily and what’s still outstanding. Nonetheless, I’ll do my best here, but if you have followups on multiple questions I do ask that you open new threads.

@Shubham_Choudhary

Let’s say I got 40% code cover coverage from the CI by Unit testing and 30% from the manual testing and total coverage of 55% using both testings.

How can I get that 55% code coverage on the SonarQube Dashboard and also “code coverage on the new code”?

For this you’re going to need to do all your testing before analysis runs, and then feed your unified report into analysis. As a side note, support for the .exec coverage report format is deprecated; replaced by XML. And, you can easily import multiple XML reports without the need to run a consolidator. Details in the docs.

@Shubham_Choudhary

In one month 1000 lines were added out of which 700 and 500 were covered by Unit and integration testing respectively and 800 distinct lines were covered. I want to get 80% “coverage on new code”.

I think what this boils down to is that you can’t access historical values for Coverage on New Code and that’s messing up the ability to do the comparisons you want to do. If I’ve correctly interpreted that, then no those historical “on New Code” values aren’t going to be available because we don’t store them. We don’t see the point saying that the “Coverage on New Code was 73% a year ago”. On New Code values are about right now.

@Shubham_Choudhary

I can think of a hack where I do a sonar scan on one-month-old code and pass the merged jacoco dump(Let’s assumed that I preserved those files) to get the total code coverage. Now I update my source code to latest and pass the jacoco dump of the latest testing to the SonarQube server to get both “total coverage” as well as “Coverage on the new code”.

One limitation I have found is that when sonar scan is going on the SCM server should also be in the same state since SonarQube does a “git blame”. So, while I did a scan on one-month-old code my SCM was is the different state given that all are happening on MASER branch.

If you’re going to do this, you need to make sure you check out the code from a month ago. Analysis will read its blame data from the checked out code, so this is not about the state of the SCM server.

 
HTH,
Ann