Channels ▼

Jolt Awards: The Best Testing Tools

, May 21, 2013 The best testing tools of the past year
  • E-mail
  • Print

Finalist: Sonar

What is code quality? My preferred definition is: Quality equals maintainability. If code can be maintained at low cost, then it is, by definition, high quality.

Open source Sonar focuses with almost disturbing intensity on this aspect of your application. It measures seven different degrees of code quality in both the static and dynamic context using pre-written, but configurable, coding style rules for more than 20 different popular languages. It has no difficulty finding errors in projects containing mixed languages, and its quality analysis can be done across a portfolio of applications.

Clever Web-based configurable dashboards, with details suitable for either high-level management types or developers, display quality metrics along with heat maps of code with quality violations. Many fine details are captured besides remedial technical debt indicated by coding style violations. For example, Sonar displays the ratio of the source code comments to source code lines. This can often reveal where there is a technical debt in readability. Sonar also detects duplicate line groups across modules or systems, giving an enormously valuable early warning about the need for potential architectural refactoring.

The feature I particularly like is the "time machine" plug-in. It allows animated continuous inspection of the evolution of code quality of a system or component over time. Thus, a component that is seen being continuously revised shows up quickly, giving advance warning about a potential longer-term design issue — a valuable insight when found early on in the project.

Sonar has previously won top awards in the Jolts (specifically, in 2009 and 2010). This year's inclusion shows that the product's continued development hews closely to the level of excellence established in earlier releases.

— Roland Racko






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.