Potential bugs violations
The three Sonar analyzers feature an extensive set of rules checking code that can lead to potential bugs and deficiencies. We are going to add to the custom Packt profile some of the most common and important rules. So far, we have added rules for Coding Standards costing a total of 100 points. For potential bugs, we will add rules to reach the target value of 200, as it is the most important part along with complexity.
To calculate the total cost/profile value, remember that each violation has a rating from 1 to 5. The higher the value, the stricter the profile becomes. For example, adding five Critical checks would raise the value of the profile to 15.
The following table breaks down the rules we will use sorted by level. Most of these checks are implemented by the Findbugs analysis engine.
|
Potential Bugs Profile Distribution | ||
|---|---|---|
|
Severity |
Rules Count |
Cost |
|
Major |
25 |
75 |
|
Critical |
25 |
100 |
|
Blocker |
5 |
25 |
|
Total Cost |
200 | |
That's a total of 55 rules at a cost...
