Java doesn’t have a really nice way to initialize the collections. Because of this creating some constant collections, passing them to a method, or using them while unit-testing is kinda way too hard. For instance; you just need a 3 items in your list, but Java expects you to define in the following way:

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.

As a software developer, everyday we’re facing with a lot of problems, tiny little bugs, or some annoying small issues. Most of them are not hard to solve (if it is not Eclipse or IBM kinda stuff :P). Maybe most of the time we’re googling a little and finding the solution, or just asking to one of our colleagues to find out what it was (if you’re thinking I’m not asking, nor googling then I’m thinking you’re a liar).