Unit Testing 2

Is your code full of if statements? Switch statements? Do you have the same switch statement in various places? When you make changes do you find yourself making the same change to the same if/switch in several places? Did you ever forget one?

This is very nice. The guy really knows how to explain things in easy to understand way! Thanks Misko!

"Guide to Writing Testable Code"

To keep our code at Google in the best possible shape we provided our software engineers with these constant reminders. Now, we are happy to share them with the world.

I found these guidelines useful not just for testing purposes but in general, it is great to have such style design. It's more readable, more understandable and have more performance.

Resource: HERE.

Unit Testing.

This is great video from Google about Unit Testing:

I really want to start doing UT in my code.

Yes, it's time consuming(it seems like this at first :) ).

Yes, the amough of code is approximatelly the same as your original code.

But hey, then you have unit tests you can easily know that all your classes and etc works correctly, you can easily catch bugs, you can easily reproduce the bugs latter.

And in the end it really helps to save time after you finish your product, because it's tested already in some cases, and if some bug happens you can easily write a test for it and see what will happen, Then you exactly will know what went wrong.

Best browser

extremetech.com made a very cool test of all top-used browsers these days,

Browsers used:

• Firefox 3.04,
  
• Chrome beta,
  
• Internet Explorer 7 (7.0.6001.18000),
  
• Opera 9.6,
  
• Safari 3.2 (526.26.13)
  

Test results

Winner

Resource: Here

IMHO:


Yeah, maybe Google Chrome is the best in speed, but I still cant use it every time, because it does't have any plugins support, that why Mozilla is my default browser, Chrome is good for fast links review, news reading, web surfing, but not for my work :)