#Sonar code quality tool code#
#Sonar code quality tool windows#

#Sonar code quality tool code#

Initially we always do a code analysis post the script development and we were fixing the issues as reported in SonarQubeвЂ™s dashboard вЂ“ like postmortem. Though there was some hesitancy, all the projects have slowly realized the value, and now it has become the regular practice of analyzing the code to find the bugs in the code and fix it. Roll-OutДЄfter the rule sets & quality gate is acknowledged by the core team we rolled it out across all the projects. Based on their response, we again re-baselined the rule set with the changes in activating/deactivating the rules, changing the severity etc. We also asked the respective teams to look into the issues reported and to provide us with their feedback. and requested them to scan their projects against the defined rules set & quality gate. We selected a couple of projects from Java. Also, the quality gate is defined with the vital measures.

#Sonar code quality tool windows#

How SonarQube turned out as a Best Practice Start SmallДЄfter our SonarQube server setup on a Windows box, with the predefined rules available in the built-in profile вЂ“ вЂSonar WayвЂ™ for each language, we examined every rule to identify the most important & suitable rules among them for the respective program languages and kept the rule set to be minimalistic. Integration with IDE like Eclipse, Visual Studio etc. Email Notification: When quality gate fails/On the status after an analysis is done.Integration with CI Engines: TFS, Jenkins etc.Gives you a moment-in-time snapshot of your code quality today, as well as trends of lagging (whatвЂ™s already gone wrong) and leading (whatвЂ™s likely to go wrong in the future) quality indicators.Quality Gate: GO/NO-GO gate for a new version of project.Dashboard: Overall quality health of all projects at a glimpse.This tool вЂSonarQubeвЂ™ not only meets our core requirements, but also had additional features built into it and with all these, it is available for вЂNOвЂ™ cost. We spent time in analyzing the various tools (free/open) that are available in the market and after scrutinizing, one tool stood out amongst all. Enforce code quality through quality gate in our organization.Continuous inspection of overall health.Though our initial goal is to automate the code review, later we realized the value of expanding this across all the projects and this article briefs about our success journey of how we achieved our objective of вЂ“ It could also enhance the outcome of the process. So, we thought about an automated way of doing the static code review that would reduce the time and cost involved in doing it. Also, issues like buffer overflows, dead code, and other subtle mistakes are tough for a human reviewer to find and are better suited to automated analysis. But, doing it manually is a tediousВ processВ and it requires skill, experience, persistence, and patience. In the past, we were reviewing our code manually with a set of coding standards. Despite being a test automation project, we always had our focus on delivering quality & clean code throughout the review process.