Why Don’t You Practice Test First Development?

...compile and registrate Csharp dllI would have said “Test Driven Development” but I want to make it clear that what I’m talking about is writing test first, or at least simultaneous to writing the code.  Not sometime after, even if that after is immediately after.

Recently, I’ve been doing some Test First Development presentations and I’m finding a trend that I’d like for you to contribute more information to.  While just about everyone I talk to will say they believe that we should be practicing Test First Development, hardly anyone is actually doing it practicing Test First Development.

So, the question I have to ask is, “Why?”

So, leave me a comment and tell me why you aren’t writing test code first.

Related Post

  • TDD Isn’t All About TestingTDD Isn’t All About Testing While the artifact of Test Driven Development is test code, what you get out of test driven development far exceeds the test themselves.  Maintainable Code By writing test first, […]
  • Using DataSets to Process XMLUsing DataSets to Process XML I started a project recently that requires me to process an XML file from Google. Being the lazy sort, I'd really rather just use the data as though it were part of a database and forget […]
  • TDD Saves Time – A StoryTDD Saves Time – A Story I recently had an experience writing code that proved to me, once again, that using Test Driven Development really is faster than the way I have been working. You will remember a couple […]
  • What Not To TestWhat Not To Test Many people believe that implementing Test Driven Development means that you need to have a test for every line of code in your system.  When  they start thinking about TDD in […]
  • ASP.NET Application_Error Detecting 404′sASP.NET Application_Error Detecting 404′s For many of you, this is going to be a "Duh!" kind of post.  But while working on this today, I found so many people asking this question and so many others giving the wrong answer, I'm […]

About Dave Bush

Dave Bush is a .NET programmer and Certified ScrumMaster who is passionate about managing risk as it relates to developing software. When he is not writing or speaking about topics related to Application Lifecycle Risk Management (ALRM), he is an example to his peers as he develops web sites in the ASP.NET environment using industry best practices.

  • Mike

    no time, things are to be done NOW!, system is big and old and not ready for ttd, writting test code is complicated – mocking objects requires a lot of preparation, like in sharepoint.

Awards & Certs