But Gregg Pollack has done the same journey as I have and he has also done this great presentation on why TDD is good and how to use it.Sadly that video is long gone. Sad, because it was a good presentation.
This is such a great presentation where he takes us through a series of points that explains the rationale of TDD and then BDD, or the “pathway to developer enlightenment”, as he calls it. I have extracted his points here:
- Testing breeds confidence
- If you write tests before you write your code, you end up writing better code
- Well written tests are just as good, if not better than documentation
- TDD isn’t about writing tests, it's about defining behavior.
Seeing this was like getting help to put words to my own thoughts. Thank you Gregg.
Also – I might have to check out Ruby. To many people has pointed towards it…
If you liked this post ... here's more for you:
Published byon Last updated