This an an archived version of the documentation for SonarQube version 4.5 & 4.5.x LTS.
See https://docs.sonarqube.org/display/SONAR/Documentation for current functionality
Just as there are seven deadly spiritual sins, which can wreck your life if you fall prey to them, there are also seven deadly development sins which can similarly wreck your code. Each of the sins is represented on the SonarQube default project dashboard, and most can additionally be tracked through issues, by adding rules from the Common Sonar repository to your quality profile.
In (mostly) no particular order, they are:
- Bugs and Potential Bugs
- Coding Standards Breach
- Lack of Unit Tests
- Bad Distribution of Complexity
- Spaghetti Design
- Not Enough or Too Many Comments
Instances of each sin increase Technical Debt, which is the effort required to undo your technical sins. Assuming you have added the Common Sonar rules to your profile, that technical debt can be tracked through SonarQube's issues mechanism. An application's technical debt can be broken down by characteristic (Technical Debt Pyramid widget).