This is my preferred approach as well. When one does this one hopefully also get a feel for what tests will be useful and which ones will be thrown out early a

This is my preferred approach as well. When one does this one hopefully also get a feel for what tests will be useful and which ones will be thrown out early and start writing more of the first ones. Couple this with a well designed language and a good IDE that can do the trivial refactorings (method rename - including catching overload collisions etc) and it becomes easy to maintain tests.