New Code Coverage has been gone and show as --

SonarQube
1

Hi All
Regard to sonar project build, we do the below steps:

  1. build one version(3.40.1-SNAPSHOT 8th May) as base line and the next build will compare to it.
    2.All of our subsequent builds will use the same version(3.42.2-SNAPSHOT) and will compare to 3.40.1-SNAPSHOT, our code will be always change and we’re still add the test for improve code coverage, so coverage on new code should always have value.

the coverage on new code is always have value before, but it’s gone and show as “–” after our newest build:

image
image983×655 34.8 KB

could someone please help me check this issue? the coverage on new code should not be null.

2

Continuing the discussion from New Code Coverage has been gone and show as –:

Hi @yz72053

I’m facing the same issue as you, and some things that I noticed… This image show that sonar find the coverage of the new code, but the measurement of the new code, does not show the difference of the coverage of the new code

image
image1542×763 40.9 KB

image
image1593×708 28.8 KB

I don’t know what I’m missing.

3

Hi,

Welcome to the community!

Normally I’d ask you not to resurrect a 2-year-old thread, but this one is still open, so… fair enough.

I can’t explain your graph, but what I see in the homepage screenshot is “0 New Lines to cover”. That tells me SonarQube didn’t find any Lines of Code in the New Code Period.

 
HTH,
Ann