Today I was digging something for one of my custom projects in JUnit’s package and I came across with very nice feature. I think it’s going to make much more sense after my first article about JUnit’s @Parameterized annotation.

In the last post, I tried to roughly touch Unit Tests and what/how many and when to test our Units. For more information about that topic, please go back to first article.

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.