Archive for the 'Agile' Category

Picture by Olivander
Some rights reserved.

Having introduced mock objects, even if you’ve managed to avoid the pitfalls described in the previous posts in this series, you can often end up with some pretty complex and ugly-looking unit tests. There might be a lot of mock objects doing very little or there may be a lot [...]


Picture by greefus groinks
Some rights reserved.

In the previous part of this series on retrofitting unit tests I talked about how you can break the unit-test as integration-test pattern by introducing mock objects. Probably the best way to do this is by using one of the many mock object toolkits out there1 . For [...]


Picture by icathing
Some rights reserved.

One of the most common mistakes I’ve found, particularly with teams who haven’t had a good deal of experience of unit testing or TDD, is that if they do have unit tests they’re often really integration tests with fake mustaches. A small, relatively self-contained piece of code needs a database [...]


Picture by hugovk
Some rights reserved.

A while ago I promised to write a few articles on the art of test-driven development or TDD1. Rather than starting with TDD itself I wanted to start by talking about what happens when you try to write unit tests after you write your code.
This can happen for any number of [...]


One of the many hats I’m wearing at work these days1 is project manager for an OEM deal we’ve done with a company that’s going to be bundling our core product with their own. As part of this I’ve had to produce several project plans and I’ve found myself reaching for Microsoft Project to [...]