Difference between revisions of "Tracking Code Quality"

From CitconWiki
Jump to navigationJump to search
Line 8: Line 8:
 
* JOODI - Package level checking. Good to enforce certain layers only access other layers e.g.
 
* JOODI - Package level checking. Good to enforce certain layers only access other layers e.g.
 
* Spec#  
 
* Spec#  
 
+
* [http://atlassian.com/clover Clover2]
=== [http://atlassian.com/clover Clover2] ===
+
** Project Risk Coverage Cloud - A tag cloud containing every class that exposes those which have low test coverage but high cyclomatic complexity
* Project Risk Coverage Cloud - A tag cloud containing every class that exposes those which have low test coverage but high cyclomatic complexity
+
** Custom Columns - Define your own quality metric by combining any of Clover's built in ones
* Custom Columns - Define your own quality metric by combining any of Clover's built in ones
+
** Track code quality over time using historical charts and reports
* Track code quality over time using historical charts and reports
 
  
 
=== References ===
 
=== References ===

Revision as of 03:13, 29 June 2008

Tracking Code Quality

  • Presentation by Marty Andrews
  • The Cyclomatic Complexity of a method is really the minimum number of unit tests needed to test very path in a method.
  • By reducing CC, usually by breaking large methods down, you reduce the number of tests you need to write !
  • Complexian - www.cogentconsulting.com.au/resources/complexian/index.html
  • FindBugs - usually needs human to interpret. Good to hook in but not run in CI. Human can run so often
  • SourceMonitor
  • JOODI - Package level checking. Good to enforce certain layers only access other layers e.g.
  • Spec#
  • Clover2
    • Project Risk Coverage Cloud - A tag cloud containing every class that exposes those which have low test coverage but high cyclomatic complexity
    • Custom Columns - Define your own quality metric by combining any of Clover's built in ones
    • Track code quality over time using historical charts and reports

References

  1. T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976
  2. B.A. Nejmeh, "NPATH: a measure of execution path complexity and its applications," Commun, ACM, vol 31, no 2, pp 188-200, 1988.
  3. Wikipedia:Cyclomatic_complexity
  4. Complexity Analyser for Java, http://www.martyandrews.net/resources/complexian.html
  5. Complexity Analyser for C++, http://gnocchi.sourceforge.net/
  6. Clover2, http://atlassian.com/clover