Regenerative Build Tools
by Michael Feathers
, May 15, 2007
Dust off an old computer and put it to work.
I think that when people look back at the way we program today, one of the things that they'll be amazed at is the fact that we have so much computing power but we don't do much with it.
Seriously, how many computers do you have? If you're like me you have a least a couple of stray ones sitting around the office, and they aren't doing anything. What a waste. And, it's only going to get worse as multicore processors become more prevalent.
When I first heard of continuous integration, way back in the day, I misunderstood it. I thought that some computer someplace was going to build my project continuously. That is, regardless of whether I or anyone else had checked in. Silly? Perhaps. But, wasteful? I don't think so, the computer is running anyway. It might as well work.
A while back, I visited a C++ team that had found a wonderful use for a spare computer. They set it up to build continuously. Then they did something fascinating. They created a script that went into their code and commented out a single #include. Then it built their project. If the build and the tests passed, the script deleted the include. If it didn't, the script uncommented the include and went on to the next one. Yes, it took quite a while to march through the code, but with that build running continuously in the background, they were able to eliminate a large number of superfluous dependencies. Their build got better.
That script that they wrote is an example of something I call a regenerative build tool. There are others. Jester is a regenerative build tool which uses mutation testing to find problems. It changes your code in subtle ways and runs your tests to see whether they still pass. If they do, you either don't have the tests you need to have, or you could have code which is really doesn't contribute to your results at all -- zombie code. Guantanamo is another regenerative build tool, a rather severe one. It deletes all code that isn't covered by a set of tests.
Labels: QA tools