How much TDD is enough TDD?

[We had a discussion at my current client about the right-level of TDD for a project under tight deadlines. This post is adapted from my contribution to that discussion] I'll start by stating that I am a huge fan of Test Driven Development. I was introduced to TDD in 2005, "got it" straight away and now, 8 years later, would not want to program without it. I'm not going to go into the benefits of TDD in this post. There are plenty of other blog posts out there that discuss that. Basically, as I said, I'm a fan – I've seen how easy it is to make changes to a well crafted TDD project and I would recommend TDD as a programming and design methodology to anyone that will listen. However…would I aim for 100% code coverage on a project? I'm not sure. You have to be pragmatic. When you have project specific time constraints, you have to look at the value that each unit test is adding. Consider a really light MVC controller action: Call a service. Use AutoMapper to map the response from a service contract to an identical view model.

✔ Read More...

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

Test Driven Development,TDD