SonarQube - unity tests code coverage on new code not working

git unit-testing sonarqube code-coverage sonarqube5.2
klodye picture klodye · Jan 25, 2016 · Viewed 11.8k times · Source

I am trying to do Sonar analysis with the unit tests code coverage on new code. When I do code coverage analysis with cobertura and do Sonar analysis the overall code coverage of the code is displayed correctly, however the code coverage of new code is not displayed.

Settings:

  • scm = Git
  • sonar.scm.disabled = false

I did following

  1. checked out earlier version of source code
  2. set Sonar project version to 1.0
  3. created Cobertura report (xml file)
  4. executed analysis and checked that the analysis was uploaded, the overal code coverage by unit tests was displayed correctly
  5. checked out latest version of source code
  6. set Sonar project version to 2.0
  7. executed analysis and checked that the analysis was uploaded, the overal code coverage by unit tests was displayed correctly

The overall code coverage of the code by unit tests got increased as I have implemented some unit tests on a code that was changed. The On New Code item in the widget however stays hidden and the code coverage of new code is not displayed.

Does any of you have any tips that could bring more light to this?

Thank you all.

Answer

Nicolas B. picture Nicolas B. · Jan 29, 2016

You're observing this behaviour because Coverage on new code currently identifies new code based on the date of the previous analysis (and not the commit date of the code previously analyzed), see SONAR-7085 .

For your scenario to work you have to force a past date for the analysis of the old code, using -Dsonar.projectDate. Good article on this right here: Sonar Time Machine : replaying the past .

Related questions

Enforcing code standards in git before commit is accepted

Alright, here's the scenario: A team of developers wants to ensure all new code matches the defined coding standards and all the unit tests are passing before a commit is accepted. Here's the trick, all of the tests need to …

Read More
Commit in git only if tests pass

I've recently started using git, and also begun unit testing (using Python's unittest module). I'd like to run my tests each time I commit, and only commit if they pass. I'm guessing I need to use pre-commit in /hooks, and …

Read More
How do I undo the most recent local commits in Git?

I accidentally committed the wrong files to Git, but didn't push the commit to the server yet. How can I undo those commits from the local repository?

Read More