Testing Legacy Code

Date Published: 27 August 2008

Testing Legacy Code


Oren wrote today about a fun problem he’d run into with trying to TDD some changes to some code about which many of his assumptions were proving incorrect. The problem is that each test he wrote that verified one of his assumptions needed to later be fixed when he found the underlying assumption wasn’t true. The result was a lot of thrashing and not a lot of productivity. The solution in this case for him was to worry first about just verifying that the code does what it does.

This caught my eye because yesterday I was talking about this very thing with Brendan and the name used by Feathers in Working Effectively with Legacy Code (myreview) eluded me. And of course, that’s been bugging me ever since but I lent my copy to another developer. So Oren’s post finally forced me to look it up – the Software Vise.

Software Vise

When we have tests that detect change, it is like having a vise around our code. The behavior of the code is fixed in place. When we make changes, we can know that we are changing only one piece of behavior at a time. In short, we’re in control of our work.

In short, when you have no tests and you’re working with legacy code that you don’t fully understand, a good place to start is to write tests that simply confirm that whatever the code does, it keeps on doing. These are often referred to as characterization tests, and I discuss them further in my Pluralsight courses on Refactoring.

Steve Smith

About Ardalis

Software Architect

Steve is an experienced software architect and trainer, focusing on code quality and Domain-Driven Design with .NET.