Analysis of PascalABC.NET using SonarQube plugins: SonarC# and PVS-Studio

[karpo...@gmail.com]

In November 2016, we posted an article about the development and use of the PVS-Studio plugin for SonarQube. We received great feedback from our customers and interested users who requested testing the plugin on a real project. As the interest in this subject is not decreasing, we decided to test the plugin on a C# project PascalABC.NET. Also, it should be borne in mind, that SonarQube have their own static analyzer of C# code - SonarC#. To make the report more complete, we decided to test SonarC# as well. The objective of this work was not the comparison of the analyzers, but the demonstration of the main peculiarities of their interaction with the SonarQube service. Plain comparison of the analyzers would not be fair due to the fact that PVS-Studio is a specialized tool for bug detection and potential vulnerabilities, while SonarQube is a service for the assessment of the code quality by a large number of parameters: code duplication, compliance with the code standards, unit tests coverage, potential bugs in the code, density of comments in the code, technical debt and so on.

Continue read article "Analysis of PascalABC.NET using SonarQube plugins: SonarC# and PVS-Studio".

[Freddy Mallet]

Hi Andrey,

Hope you're doing well and thanks for this article. Call it whatever you want but this is a comparison between SonarC# and PVS-Studio. But that's fine because I think this comparison is fair enough and I agree with the main conclusion: SonarC# is currently noisier than PVS-Studio. The good point is that we were already aware of this level of noise and all our efforts are currently focused to kill this noise and make our mainstream code analyzers not generating more than 10% of irrelevant issues (from a end-user perspective). This is the main color of all the latest and upcoming versions of SonarJava, SonarJS, SonarCOBOL, SonarC# and SonarCFamily. 

Moreover, as we know together that our internal dataflow engines are equally powerful, looks like the competition can officially start. So feel free to do another fair status update of this article each 2 months, we love challenges ;)

Cheers

Freddy

On Wed, Mar 29, 2017 at 1:29 PM <karpo...@gmail.com> wrote:

In November 2016, we posted an article about the development and use of the PVS-Studio plugin for SonarQube. We received great feedback from our customers and interested users who requested testing the plugin on a real project. As the interest in this subject is not decreasing, we decided to test the plugin on a C# project PascalABC.NET. Also, it should be borne in mind, that SonarQube have their own static analyzer of C# code - SonarC#. To make the report more complete, we decided to test SonarC# as well. The objective of this work was not the comparison of the analyzers, but the demonstration of the main peculiarities of their interaction with the SonarQube service. Plain comparison of the analyzers would not be fair due to the fact that PVS-Studio is a specialized tool for bug detection and potential vulnerabilities, while SonarQube is a service for the assessment of the code quality by a large number of parameters: code duplication, compliance with the code standards, unit tests coverage, potential bugs in the code, density of comments in the code, technical debt and so on.

Continue read article "Analysis of PascalABC.NET using SonarQube plugins: SonarC# and PVS-Studio".

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/f7670805-a530-460b-ba75-4e124e93b448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Freddy MALLET | SonarSource

Co-Founder
http://sonarsource.com