The Sonar team is very proud to announce Sonar 2.0, the first release of 2010. As announced in a previous post, the main feature in Sonar 2.0 consists of analyzing Design : Architecture and object oriented metrics. This enables to report on the “7th deadly sin of the developer” that was missing so far in Sonar. As a reminder, here are the first six deadly sins : low coverage by unit tests, bad complexity distribution, potential bugs, duplicated code, lack of comments and non respect of coding standards.
As it is now a tradition, here is a presentation of the new features in screenshots. Enjoy !

Read the rest of this page »

Here comes the 8th and last major Sonar release of the year. Like for all previous releases, this post is a summary of the new features through screenshots :

Read the rest of this page »

We’re happy to announce the release of Sonar 1.11. This new version contains more than 60 issues that have been resolved amongst which improvements, bug fixes, technical migrations and also several new features. Here are the most important ones in screenshots :

Read the rest of this page »

We’re happy to announce the release of Sonar 1.10. This new version contains more than 40 improvements and bug fixes and also contains several new features. Here are the most important in screenshots :

Settings at project level

Most of the settings can now be overridden on projects. This enables to have a default behavior and then specific configuration for projects without having to amend poms.

Read the rest of this page »

It is almost a tradition now : every month, we release a new version of Sonar. I am sure you are impatient to know which killing functionality is gonna be in version 1.9… Well, this month the new features are going to be difficult to show through screenshots…

Read the rest of this page »

Sonar 1.9 has just been released : installing this new version implies to be aware a few things. I’m not talking here about any technical complexity to upgrade from previous releases but about functional evolutions.
So far, the standard metrics (number of classes, number of comments, cyclomatic complexity…) were gathered using the well known JavaNCSS. However, as mentioned in a previous post, the metrics calculated by the current version of JavaNCSS has some flaws (creating new metrics is pretty difficult, comments are not available at class level), suffers approximations (nested classes are not managed) and crashes on certain code patterns (annotations, generics, none UTF8 characters). Therefore we have decided to proceed with a complete rewrite of JavaNCSS that we named sonar-squid.

Read the rest of this page »

We’re happy to announce the availability of April’s release : Sonar 1.8. This new version, ready to go into production, contains several improvements and bug fixes. Here are the most important of them in screenshots :

Hotspots

This service enables at any level (project, module or package) to display the classes that have the most… and the less… Moreover, we are introducing a new metric that compounds code coverage and complexity of the class. This new metric’s objective is to highlight the classes to work on when you want to quickly increase your code coverage.

Read the rest of this page »

Sonar 1.7 has been released. This new version contains several improvements among which a much better compatibility with IE 6. On top of this, Sonar 1.7 has new features :

Exclude packages and classes

Most of the time, there is no need to evaluate generated sources. It is now possible to exclude them from analysis.

Viewing the unit tests results

Need to know which tests failed and why ?

Viewing lines that are duplicated

Coverage clouds on modules and packages

The functionality was already available at project level : it has been extended to modules and packages.

For more information, you can read the full release notes.

Sonar 1.6 has been released. On top of various bug-fixes and several improvements, it contains 3 new major features related to the management of quality profiles.

Define measure thresholds

It is now possible to define thresholds and to trigger alerts on metrics, for example if the code coverage is less than 35% or if complexity by class is greater than 40… On any metric, there are two levels of thresholds : warning and error

Read the rest of this page »

We have taken a few screenshots of the next release, just to make you want to try the 1.5 release candidate 1 !

Code coverage details

The Code Coverage report shows which lines of code were hit – or not – by unit tests. It works whatever the selected coverage tool, Cobertura (by default) or Atlassian Clover.

Improve Coding Rules Compliance

Simply visualize kinds of coding rules violations.

Clouds of risky classes

Mix complexity and code coverage measures to graphically discover which classes are the most risky. Big red classes are the most complex and the less tested.

Search Coding Rules

Search coding rules by name, plugin, activation level or category. Results can be exported in CSV format. Did you notice the name of the plugin selected in the screenshot ? Yes, it’s well-known Findbugs, integrated besides Checkstyle and PMD.

Search engine on projects

Quickly access to project dashboards. The search bar is always accessible from the header. Just start typing the name of the project you search.

Better Coding Rules Breakdown

Compare metrics on time machine

Compare trends of any measures on the same chart, for example to see if code coverage is related to complexity.

Centralized Atlassian Clover license

Simplify the Clover configuration, just copy the Clover license once in sonar and it will be available to all of your projects.