Skip to main content


Showing posts from 2015

Using TestDriven.NET and NCover to benchmark and monitor unit test code coverage

I wrote this blog post about a year ago - have finally got around to putting it online. It uses a "genericised" system called UpdateManager to demonstrate how to set up code coverage analysis for .NET. Hopefully it's not too dated just yet...
What is unit test code coverage benchmarking/analysis? Unit test code coverage analysis essentially tells us "how much of my codebase is covered (or "exercised") by my unit test suite?" When we are writing unit tests, it is necessary to visually scan the codebase and get a feel for what degree of coverage we have and what parts of the codebase are important/relevant for unit test. Setting up a benchmark such as "a standard .NET codebase must have at least 70% unit test coverage" can be useful, as although this is not a fail-safe way to make sure that we are testing the right things, we can at least be certain that if our metrics indicate we meet the benchmark, most of the important stuff will be tested. …

The importance of improvisation

Preamble, background, etcScrum is a process improvement framework that has grown up within the world of software development and/but is increasingly used not only within the world of software, but outside of it also. Scrum in-fact lends itself well to product development in general. This post focuses on Scrum (and frameworks like it); in particular how it copes (or doesn't cope) with significant organisational change and where/when improvisation becomes more important than a framework.

The following links provide some information about Scrum:
A 1986 HBR article that introduces the basic concepts: Wikipedia page on Scrum: acquaintance of mine recently asked an interesting question about Scrum...which was essentially: 

"What do you do when an established Scrum team encounters a serious problem?" 

["What do you do...what do you do...?…