Tuesday, August 2, 2011

TDD Or Not TDD Guest blog by @avi_kaye

 

Test Driven Design, or TDD, is one of the leading development methodologies in the world today. The premise is simple - developers test their code while writing it to prevent bugs from occurring. In TDD, to-be-or-not-to-be-developers first write a test, which fails, then they write the code to pass the test.
Remember that sinking feeling when it’s getting close to the release date? Between developers writing code, QA testing code, and developers writing more code to fix bugs, the launch time just keeps getting pushed back, while all the time customers are waiting to get their software. That’s exactly the kind of situation TDD prevents. The QA gets code that is already extensively tested, and when a bug does make it through the cracks, developers can find the problem much faster.
So if you want to be able to manage your release cycles better, ship higher quality software and improve the productivity of your development team - TDD is the way to go.
To learn more, check out the upcoming Three Day TDD .NET Course presented by Lior Friedman, Agile Coach and software craftsman.

 

Tal Druyan