10 habits of highly in-efficient tester

1) Believe in Assumptions: Core aim of testing is to defy assumptions. If the tester is having assumptions (and that too not getting clearification around those) then it will be very dangerous.
Testing means trying different scenarios where some bugs may or may not be expected.
If the tester is assuming that the developer is right or the code is already tested once or the end customer is not using this platform or this application is running from last 10 months why will it crash now...then you can be sure that the product will be left untested...
2) Not using his thinking power, if the tester can not imagine sscenarios, if he can not replicate the user then he is not an efficient tester...

remaining habits to be shared later..Enjoy reading

Google Chrome Beta is out...

the latest buzz in town...Google came with a bang and this time with none other than Chrome.
The killer browser (for definitely) killing Microsoft Internet Explorer, Opera browser, Firefox etc....

The damage has already started with lots and lots of internet users moving to Chrome. I too tried for 1.5 weeks but I am really fed up with chrome...I am moving back to IE and installed the beta version of IE 8.
Google Chorme is nothing but a mix of all best qualities from each browser and since Google has no issues on the infrastructure/customer base/applications they are able to push Chrome so far...Old concepts in new bottle, I have already crashed Chrome 3-4 times with my testing...

Let's see what all you have to say...and yes their Comic Strip was really nice...