Add scoverage metrics and reports #3
Conversation
added maven samples with README
…ork correctly for maven package
Fixed coverage reporting in sonar - instrumentation should now also w…
The stub parser is not used anymore, removed it
Justification: relying on getParentFile gets the path splitting working under windows and unix - adapted the tests to the new behavior - added a windows / unix switch in the tests to get them working on both systems PathUtils now converts: - the empty path to an empty List - an absolute path to a list folders (not including the drive name under windows) - a relative path to a list of folders
Justification:
- sanitizing the reported file pathes to a common format makes the sensor simpler
- it is a precondition for implementing proper directory coverage
- tests run now under unix and windows, easier to develop
The sonar.sources property can be read from the settings. By mapping all
reported pathes (absolute / base dir relative / source dir relative) against
the actual file tree it is possible to converte all of them to the same
source dir relative format.
For instance
/home/src/main/scala/folder/test0.scala => folder/test0.scala
folder/test1.scala => folder/test1.scala
/src/main/scala/test2.scala => test2.scala
...
- testing absolute report file paths - testing base dir relative report file paths - testing source dir relative report file paths
If the core metric STATEMENTS value is already set scoverage will not overwrite the value but the existing value will also not align with the covered statement values. Using a separated value solves this problem - Added totalStatements to the plugin metrics
The SonarQube treemap widgets work better if metrics exist for the project, the directory and the file level. Project coverage is defined as sum of ALL children Directory coverage is defined as sum of the DIRECT children The directories have to be treated special because the SonarQube treemap displays all directories on the same level (not as a tree). Using full sums would hide bad coverage results in some cases.
- measures should be saved for all levels (directory, project, module, file) - the sum should not be necessary any more - makes the two metrics more similar, a correct "sum" for the coverage value cannot be defined as easily.
fix link syntax, link to releases
Improved path handling, reported filenames are converted to src dir relative paths
Adding directory coverage thus supporting the Treemap widget
…overage Added total statements metric to avoid overlaps with coremetrics
…ter' into staging
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings:
Status must start with one of the followings: |
No description provided.