VinodAnandan / sonar-pitest

43 stars 30 forks source link

No code coverage displayed on sonar #18

Closed sbuisson closed 6 years ago

sbuisson commented 6 years ago

The mutations found arent display on the lines of the files

bradflood commented 6 years ago

I plan to start work on this soon.

sbuisson commented 6 years ago

@bradflood About-it : I find the default html report of pitest very easy to read, Do you know if it's possible to display-it in sonar?

bradflood commented 6 years ago

@sbuisson I don't envision the pitest html report being displayed as-is within sonarqube. The value of sonarqube is that the individual mutations can be translated into SQ issues, and then we can see the "test quality" information in the context of everything else that SQ is reporting on. I would think we could create a pitest-only report using SQ if we wanted to, after the pitest info has been processed in SQ

bradflood commented 6 years ago

@sbuisson I think I found a way to create something similar to the default html report you indicate. Before I do that, could you review 0.9-SNAPSHOT, which creates Issues with tags "test-quality" and "test-coverage" and let me know if that provides good enough capabilities?

https://github.com/stevespringett/dependency-check-sonar-plugin/pull/40/commits/b1456dadbb031cf5429f1eeb7bc7bd22f6c79082