maven - Excluded classes still counting towards total coverage result -
We recently upgraded to SonarCube 4.3.2. In the previous version (it does not remember what it was), it was possible to select JACOO as a code quoors analyzer and it was possible to define Maven as a simple asset;
For example
With this version of SonarCube, there is no alternative to selecting JACOO so I am trying to work it in any other way. There are many posts about this topic but none of them solves my problem. I managed to get out of the class, but they show the SonCube as 0% (and bring down total coverage). Except the above assets, it now works.
In my Palm, I have added the following plugin:
& Lt; Version & gt; 0.6.0.201210061924 & lt; / Edition & gt; & Lt; Configuration & gt; & Lt; Exclude & gt; & Lt; To exit & gt; ** / SonarTest * & lt; / Exclude & gt; & Lt; / Not included & gt; & Lt; / Configuration & gt; & Lt; Hanging & gt; & Lt; Execution & gt; & Lt; Goals & gt; & Lt; Goal & gt; Ready-Agent & lt; / Target & gt; & Lt; / Targets & gt; & Lt; / Execution & gt; & Lt; Execution & gt; & Lt; ID & gt; Report & lt; / Id & gt; & Lt; Step & gt; Ready package & lt; / Step & gt; & Lt; Goals & gt; & Lt; Goal & gt; Report & lt; / Target & gt; & Lt; / Targets & gt; & Lt; / Execution & gt; & Lt; / Hanging & gt; & Lt; / Plugin & gt;
The configuration looks okay because the class is completely excluded in the Jaco report. Sonartest has been partially tested but with this configuration it is shown as 0% in sonar, it seems that the exclusion is working to make some expansion. How can I inform Sonar that these exclusionary sections should be completely ignored on the basis of coverage.
I believe that you will find your answer on
Comments
Post a Comment