Tracking Code Quality - Revision history

JerryShea: /* Industry standard CCN numbers */

2008-06-29T21:55:24Z

Industry standard CCN numbers

JerryShea: /* Tracking Code Quality */

2008-06-29T21:52:37Z

Tracking Code Quality

JerryShea: /* Tracking Code Quality */

2008-06-29T21:43:56Z

Tracking Code Quality

124.170.23.178 at 10:13, 29 June 2008

2008-06-29T10:13:29Z

124.170.23.178: /* Tracking Code Quality */

2008-06-29T10:12:12Z

Tracking Code Quality

Gommo at 08:42, 29 June 2008

2008-06-29T08:42:16Z

Epronk: New page: References: # T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976 # B.A. Nejmeh, "NPATH: a measure of execution path complexity and its applica...

2008-06-28T10:43:23Z

New page: References: # T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976 # B.A. Nejmeh, "NPATH: a measure of execution path complexity and its applica...

New page

References:

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

@@ Line 14: / Line 14: @@
 === Industry standard CCN numbers ===
-* There was some discussion over what is an unacceptably high CCN. I ([JerryShea]) don't like to see CCN above 20 personally. I have seen this table reproduced in a few places, including [http://www.linuxjournal.com/article/8035 this linuxjournal article]:
+* There was some discussion over what is an unacceptably high CCN. I ([[User:JerryShea|JerryShea]]) don't like to see CCN above 20 personally. I have seen this table reproduced in a few places, including [http://www.linuxjournal.com/article/8035 this linuxjournal article]:
 {| class="wikitable"
 |-

@@ Line 2: / Line 2: @@
 * Presentation by Marty Andrews
 * The [http://en.wikipedia.org/wiki/Cyclomatic_complexity 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 !
+* 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
@@ Line 12: / Line 12: @@
 ** 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 ===

@@ Line 1: / Line 1: @@
 == 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.
+* The [http://en.wikipedia.org/wiki/Cyclomatic_complexity 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
@@ Line 17: / Line 17: @@
 # T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976
 # B.A. Nejmeh, "NPATH: a measure of execution path complexity and its applications," Commun, ACM, vol 31, no 2, pp 188-200, 1988.
-# Wikipedia:Cyclomatic_complexity
+# [http://en.wikipedia.org/wiki/Cyclomatic_complexity Wikipedia:Cyclomatic_complexity]
 # Complexity Analyser for Java, http://www.martyandrews.net/resources/complexian.html
 # Complexity Analyser for C++, http://gnocchi.sourceforge.net/
 # Clover2, http://atlassian.com/clover

@@ Line 8: / Line 8: @@
 * JOODI - Package level checking. Good to enforce certain layers only access other layers e.g.
 * 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
 === References ===

@@ Line 8: / Line 8: @@
 * JOODI - Package level checking. Good to enforce certain layers only access other layers e.g.
 * Spec#
 === References ===
@@ Line 16: / Line 21: @@
 # Complexity Analyser for Java, http://www.martyandrews.net/resources/complexian.html
 # Complexity Analyser for C++, http://gnocchi.sourceforge.net/

← Older revision		Revision as of 08:42, 29 June 2008
Line 1:		Line 1:
−	References:	+	== 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#
		+
		+	=== References ===

	# T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976		# T.J. McCabe, "A complexity measure," IEEE Trans. Software Eng. vol. SE2, no 4, pp 308-320, 1976