I use a mixture. If it's a Java method, I use test-after, by which I mean after the method is written, some times after the core of the class. Most of the tim

I use a mixture. If it's a Java method, I use test-after, by which I mean after the method is written, some times after the core of the class. Most of the time I am not working from specs, so I find TDD interrupts the design/implementation flow. Often I dont know the complete signature until I have written it. If the method is complex, it often gets a couple of refactorings along the way. The case where I consistently test before is a method doing database queries. I find it much less tedious to write and test pure SQL before any java.