开发者

Recommended configuration for Sonar alerts?

Our project is using Sonar to analyze and measure technical qua开发者_如何转开发lity. There is an overwhelming range of metrics available, along with the possibility to configure visual alerts when metrics drop below a specified threshold.

Are there any decent guidelines available on which Sonar alerts are useful for typical projects, and what threshold values might be sensible?


I can only giva advice according to my own experience. I don't know of any guides / best practises.

I use them to mark undesired states:

  1. major code goals I want to achieve (Blockers > 1 --> RED)
  2. minor goals I want to achieve (Criticals > 30 --> RED)

I also find it useful to mark metrics, that have been achieved like:

  1. code-coverage (Drops under 80% --> RED), architecture tange index < 70% ...

So basically I use the alerts to mark undesired states, to warn if certain metrics fail to achieve a value.

I find the options in sonar very overwhelming, so I picked metrcis that sounded useful or were coherent with current refactoring plans.

I hope this helps a bit :)

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜