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...

Grapevine - The Power of Rumours

Hi,

I am doing a sort of research on the power of rumours which when nicely planned can help in getting the nice feedback before the actual decision is to be made.
All Rumours are not 100% bogus, there are some ways say as Grapevine where the roumours can be crafted in such a way to get early feedback before getting the public respose...

my recent visit for Campus Interview

last week I went to one of the prestigious engineering college (in UP) for selecting few engineers for my company. The response was really great, 160+ people appeared for written test and finally 42 could clear the round 1.
During the interview session, I felt that the student's knowledge base is not upto mark (which we as a company expects). They have the bookish knowledge but not practical aspects of using the same theorm/logic. All were speaking the same answers, seems like there is a strong need of teaching them what exactly we as a company wants in them. what to speak, what not to speak, what areas to focus and what areas to simply ignore in calling out in interviews. what should be the body language etc...we could finally select only 5 candidates from the 165 odd batch...
Had they been trained in campus interviews training, they could have got good number of offers.

Cut Piracy, Get more Jobs

Reducing software piracy in India by ten per cent over the next four years can generate an additional 44,000 new IT jobs, $3.1 billion in economic growth, and $200 million in tax revenues, according to a study released today by the Business Software Alliance (BSA). The study predicts an additional $208 million in revenues to local vendors alone. Further, reducing software piracy in Asia by just ten percentage points can generate 435,000 new jobs, over $40 billion in economic growth, and over $5 billion in tax revenues above current projections, the study revealed.

(sources: Ciol.com)