Disclaimer:
I’m not going to talk about trivial things such as unit testing, etc. The goal here is to hand pick some less well-known tools/practices and
show how to use them.
6
7
10
-Example: for trends,
tracking stuff. For example mean time between a bug is fixed.
Or number of tests. Or code reviews (active = pair programming or distributed pair programming when IDEs support it)
-Problem with passive quality is that you need to look at it for it
to have any effect, whereas activate quality is
always applied.
-Active quality very
important when working within a team (distributed or not)
to maintain consistency in quality
-Active quality
is a way to increase project quality without requiring extra budget
11
12
-Most m1 plugins are there
-Dashboard missing
13
14
This is much better than m1 because
-No need to depend on relative paths
-Easy to share between any number of projects
Explain
strategies
15
16
Example
of a Clirr report: http://cargo.codehaus.org/Release+notes+for+Cargo+0.8