Oh bugger, you can tell I don't do much .Net work!

---

This was probably the least troll like and most constructive criticism I have ever received. I agree with much of what you are saying. To be honest what I've done feels like a form of automated walk through break points.

I am not 100% clear on the difference between TDD and unit testing. I think TDD is simply writing a unit test (too early:hehe:) before coding where as it is perfectly possible to write it afterwards.

Some developers I know argue like cat, dog and ferret over the merit of BDD vs TDD vs building tests after coding. I don't think there is any clear winner. Frankly, I come down on the side that gets stuff done which ever one that might be.

For me the trick with TDD is coming up with a test that genuinely does add value and does drive the development forward. It's a tool that helped me by helping me think the problem through. I'm not going to evangelise it because I know not everyone gets the same benefit.