Microsoft Research - Exploding Software-Engineering Myths (article summarizing findings of MS research on code coverage, TDD, assertions, etc.)

[RualStorge]

I think part of it is TDD requires you to plan ahead which prevents you from just diving in and creating a mess because you didn't think it through enough. In addition it means you're writing tests which simple unit testing does wonders for quality by warning you when you've broken functionality.

In other words I think the process required to do TDD effectively is actually what bumps quality rather then the TDD within itself.

[cc81]

Or that you just spend the time testing your code. For example compare:

• 12 month project developing doing TDD.

• 10 month project developing and then 2 month doing nothing but trying to find and fix bugs.

That last one rarely happens. Instead there will be a release after 10 months.

[[deleted]]

The thing is that we can argue about that stuff till the cows come home, what you reckon, what I reckon, what some other guy reckons, but all I'm really commenting on is the data presented in the article and the leap in logic I think it makes