The Sonar team is proud to announce the release of Sonar 3.1. This new version includes several major features that we believe are worth stopping your daily work for a couple of minutes to check out: global dashboards, violations on unit tests, Single Sign-On, integration of FindBugs 2.0 and creation of JIRA issues from violations.
It has now been almost 2 years since JaCoCo was integrated as a plugin in Sonar and more than 18 months since Evgeny published his post to describe how to Measure Code Coverage by Integration Tests with Sonar....
During my IT life I had to analyze many code bases – something that you would call an architecture review. Or some might call it a part of architecture review. As for me, I don’t believe in reviews without actively touching the source code. Touching means: static analysis, load and stress tests and manual walk-throughs.
On May 31, 17:00 CEST SonarSource is going to host a live online webinar about Sonar 3.0. The objective of the webinar is to introduce the feature set of Sonar 3.0 and also to go through the vision for the platform as well as its roadmap.
Sonar 3.0 helps keep source code cleanThe HSonarSource has announced the release of version 3.0 of the Sonar code quality assurance tool. New features allow users to quickly spot quality violations and ascertain the test coverage of new code.
The Sonar team is proud to announce the release of Sonar 3.0.
The team has been working for the last 2 years on Sonar 2.x versions, adding support for Continuous Inspection to manage Technical Debt. With Sonar 2.14, we felt that we had reach functional maturity for this support and that adding stability would make it a great candidate for a major release: Sonar 3.0.
When we talk about the quality of software, we must refine the discussion to make it clear whether we are talking about internal or external quality. External quality refers to the software’s presentation and behavior from a user or customer’s perspective. Internal quality refers to how the software was constructed, and how easy it might be to maintain or extend.
This example shows how to generate coverage for unit and integration tests using Maven and Sonar. It uses very simple techniques and should only take 10-15 minutes to get running in any existing Maven build. It can be used across unit, integration, ATDD or any other kind of test suite. The coverage results are shown in Sonar.
Things had been quiet at SonarSource headquarters recently; not because they were just resting on previous releases, but because they were working tirelessly towards the next stable release of the code quality manager, ...
SonarSource has announced a major new version of its platform for continuous inspection of code quality. Sonar 3.0 is the most stable and complete release to date, focused on taking ongoing code-quality management to the ...