Build Up To Something

This is an article written by Mike Clark on January 2004 titled “A Dozen Ways to Get the Testing Bug in the New Year”.

The article can be read and printed through the this URL.

Test-driven development received a lot of attention in 2003, and the interest will grow in 2004. For good reason: everyone agrees testing is important, but now many respected programmers are claiming that by writing tests first, they see better designs emerge. These same programmers quickly point out that test-driven development makes them feel more productive and less stressed. At the end of a shorter programming day they’ve built a suite of passing tests and code with better designs. Sound too good to be true? Well, there’s nothing to lose in giving it a whirl. In fact, there’s much to be gained.

This article gives you 12 practical ways to start writing tests, and keep writing tests, regardless of your development process. The first two techniques play off of things you’re probably already doing, so you don’t have to move too far out of your comfort zone. The next two challenge you to wade deeper into the pool to realize the benefits of test-driven development. The remaining techniques round out the regimen to keep you testing effectively all year. You’ll be well on your way to fulfilling your new year’s resolutions. Caution:
contents have been known to be infectious!

Summary: Getting started writing tests doesn’t have to be difficult or time-consuming. Just wade in gradually by spotting practical opportunities to let your computer automatically check what you’re already checking manually. Before writing new code, assert your expectations about what it should do. Along the way, listen to the tests for design insights. Make testing an integral part of your development process by writing tests first and making it easy for anyone on your team to run all the tests at any time. Finally, don’t go it alone.