Comments on: Measuring Code Integrity

By: Development and Integrity Management by Eli Lopian » Measuring Effective Unit Tests

Mon, 13 Jul 2009 13:17:14 +0000

[...] I have debate this before (Measuring Code Integrity) and I think that measuring the Bug Fix Time is a direct measurement of the effectiveness of our unit tests. I have written a small application that sits on the developers desktop and we are starting to use it in Typemock. [...]

By: Eli Lopian

Eli Lopian — Tue, 09 Jun 2009 08:37:29 +0000

Hi Andy,
I am not talking about static analysis at all. I am talking about *logical* bugs, not *syntactic* ones.
Code Integrity is that the code DOES what it is supposed to DO. We need a suite of automated logical unit tests to make sure that our code is in integrity, and to manage this we need to measure our code integrity, we can do this by measuring our Bug Fix Time, our goal is to bring that number down, because the longer it takes to fix a bug, the less integrity our code has.

By: Andy

Andy — Mon, 08 Jun 2009 21:18:20 +0000

87% is a very high number – thanks for publishing! I’ve always wondered if there was a similar metric for static analysis tools (source code analysis). Static analysis tools may report a number of false positives or “don’t cares” and so organizations always want to measure whether they are investing the right time and energy into static analysis.