Test Driven Development is not bad, mkay?

Bucky, who seems to write a bile-ish blog, thinks that test driven development is bad because he doesn’t like compile errors in his code. Because of that, he suggests writing the interface first.

I would suggest that the modern IDE’s make the “write a test that doesn’t compile” stage easier. Looking at a tool like Eclipse: I can write a call to a method that doesn’t exist, then click on the call and create the method from it.

Also, a large part of what TDD is about is evolving the interface as part of the process of writing the tests. That’s why it’s test-driven development; writing the tests drives the detail focus of your design. Writing the interface first breaks this paradigm; you may well still be working in a thorough and professional way, but it’s not TDD (not that there’s anything wrong with that)

PS: Before any of the Thoughtworkers (hi guys 😉 makes this comment, I’ll do it: Test-Driven Development Is Not About Testing

Author: Robert Watkins

My name is Robert Watkins. I am a software developer and have been for over 18 years now. I currently work for people, but my opinions here are in no way endorsed by them (which is cool; their opinions aren’t endorsed by me either). My main professional interests are in Java development, using Agile methods, with a historical focus on building web based applications. I’m also a Mac-fan and love my iPhone, which I’m currently learning how to code for. I live and work in Brisbane, Australia, but I grew up in the Northern Territory, and still find Brisbane too cold (after 16 years here). I’m married, with two children and one cat. My politics are socialist in tendency, my religious affiliation is atheist (aka “none of the above”), my attitude is condescending and my moral standing is lying down. View all posts by Robert Watkins