I 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.
Like this Article? Subscribe to get every article sent to your email.
- YAGNI – You Aren’t Going To Need It One of the design principles in software development is to only write what you need today. This has taken on the moniker of YAGNI (You Aren’t Going To Need It). The question is, […]
- Using 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 […]
- Is Your Architecture Crippling Your Unit Testing? Last week I wrote a post that talked about Unit Testing and the need to make sure you are only testing one particular unit of code at a time. The post was well received. But […]
- TDD 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, […]
- What’s In My Blogging Toolbox? So as I thought this week about what I might write, I decided to review the various tools that I use to get stuff done. I started this post with the stuff I use to create the blog […]
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.