Today I was reading an article that Martin Fowler has recently added to his blog like couple months back. The article was about Lean (Scrum) process and its poor applications by missing the point.

Good question if you really don’t know what it means :) I’ve more than 7 years of software development experience and to be honest, I’ve never seen a company who uses code coverage as a metric unfortunately. We’re developing a lot of beautiful software and in most cases we’re ending up with lots of code messes :( You can argue on why it happens like this, but I’m not gonna go into that today. Let’s get back to the main topic:

I remember my generation and how we were having trouble with understanding Test Driven Development (Design). First it came like TFD (Test First Development) which you were writing your tests before going into any code. But then this doesn’t fit into practical world. And TDD came into our world. Right now in turns into TED (Test Enhanced Design). Hehe.. Anyway, I just want to share my experience with all these. If you’re just starting this technique, you might find it a little bit hard to identify what/how many and when you should use this technique. And maybe more interesting, what is all about? what is unit test, what is integration test, what is functional test, what is acceptance test, etc.