Hey everybody.
We are using Pitest in our build pipeline for the past year. It runs as an additional build step in every main build, but we haven’t implemented any feedback cycle. This means that no developer is informed if mutation coverage or test strength decreases.
Currently, our Jenkins build generates a Pitest report and zips it. I occasionally take a look at these reports.
I was hoping to find a Sonar plugin that could visualize these numbers over time. Since we regularly use Sonar, it would be convenient. I found this plugin here (https://github.com/VinodAnandan/sonar-pitest), but it seems to be outdated (no commits in the last 7 years), and it doesn’t appear to be compatible with Sonar 9.
The only alternative I see is to define thresholds so that the build fails if the target threshold is not reached. However, this solution doesn’t quite satisfy me.
How do you integrate Pitest into your daily workflow?
--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pitusers/2aa8f95e-3889-4f39-aa4b-f1766901cd8en%40googlegroups.com.