views:

209

answers:

7

What tools/libraries do you run along with your build to assess and maintain quality?

As part of my CI (Cruise Control) builds I run:
Simian
Nunit
Ncover
Ndepend
FxCop
as part of Nant

I am looking for tools to instrument complexities, metrics, etc .

+2  A: 

ANTS Profiler

Adam Robinson
+2  A: 

The only thing I run as part of my regular build is Nunit, and some simple tweaks to deal with version maintenance.

My view is that the rest of the tools are useful when trying to solve a specific problem, but that you shouldn't spend all your time worrying about arbitrary numbers, "zone of pain", etc.

Don't get me wrong - I very much use the other tools (or variants of them, such as dotTrace) - but more "on demand" (with code coverage being the most regular that I use).

Marc Gravell
Marc, do you know that NDepend can help a lot churning code coverage data? See here: http://codebetter.com/blogs/patricksmacchia/archive/2008/04/09/make-the-most-of-your-test-coverage-data.aspx
Patrick Smacchia - NDepend dev
Thanks for the extra info
Marc Gravell
+2  A: 

I just heard of StyleCop today on SO

Jacob Adams
+1  A: 

Why don't you use some NDepend's CQL rules to address all facets of quality (metric, structure, coverage, evolution, side effects, dead code, naming coherence...). All this is described on this post: Write active conventions on your code base

Patrick Smacchia - NDepend dev
+1  A: 

One I saw yesterday
Vil

Cherian
+1  A: 

also dotProfiler and you can use buitin metric in visual studio team suite

Adinochestva
A: 

UppercuT.

It uses the following to analyze code:

  • NUnit OR MbUnit
  • NCover
  • NDepend

UppercuT uses NAnt to build and it is the insanely easy to use Build Framework!

http://code.google.com/p/uppercut/

Some good explanations here: UppercuT

ferventcoder