SonarQube Java

The IT and Overall code coverage should not be computed when the code coverage by unit tests is not computed with jacoco

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Component/s: JaCoCo
  • Labels:
    None
  • Number of attachments :
    0

Description

for the time being overall code coverage = integration test coverage

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment -

Manually tested !

Show
Freddy Mallet added a comment - Manually tested !
Hide
Permalink
sam hendley added a comment -

I was about to post a bug about "Overall coverage" not being calculated if there is no Unit coverage when I found this. Is that expected behavior? I think it leads to odd results if we dont consider a package with only integration testing to have an "overall coverage" number.

Show
sam hendley added a comment - I was about to post a bug about "Overall coverage" not being calculated if there is no Unit coverage when I found this. Is that expected behavior? I think it leads to odd results if we dont consider a package with only integration testing to have an "overall coverage" number.
Hide
Permalink
sam hendley added a comment -

Here is a link to what it looks like now:

http://imgur.com/IlHyAxN

Show
sam hendley added a comment - Here is a link to what it looks like now: http://imgur.com/IlHyAxN

People

  • Assignee:
    David Gageot
    Reporter:
    Freddy Mallet
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: