In developers we Trust. The rest we Test.

The old school philosophy of testing is "Break the software". I used to think this way and be driven this way. Then I realized something, when my focus is on breaking something, my approach is attack mode..... If I want to break a glass vase, I throw it down and it breaks. If I want to break my software, I find vulnerable spots and take a jab at it. Then what? I report, "hey, its broken" and probably feel proud that "Hey, I broke it!!" Then what? I don't know.  I am not sure if this approach every worked for me. I usually fall in love with most products I work on. They are my babies. I want the best for them. I want them to evolve and improve. I want them to co-exist with their sibling applications. I want them to have a unique name in the software industries. I want to give them the best opportunities I can provide with my team. It takes a village It take a village to raise a kid. It takes a team to create a prod

(Not to be mistaken for the pencil test)  If the requirement for a pencil was to write 10 pages, and during testing the pencil ended up writing 12 pages. What should the testers do? Pass it or fail? Should the testers PASS the pencil test because the result was better than expected? Should the testers FAIL the pencil test because the result was not per spec? May the testers ask for more specs regarding the weight and thickness of the overall pencil? May the testers ask for more specs regarding the weight and thickness of the lead core? Should the testers re-test the darkness of the writing? Should the testers use other kinds of paper for executing re-testing? What would you do as a tester? Why should you do anything else besides testing and giving a pass or fail? Possible defects –  Longer pencil than mentioned in spec Thinner lead core than mentioned in spec; Possible concerns –  More money is being spent on the pencil Less return of investment may be the resul

No wonder most Software out there is f...ed up and violated!! According to Freud - the unconscious mind and the primary motivation for all things in life is sex. So, I am comparing software testing  behavior to making love during my leisure (bored out of mind) time. One more reason for doing this - both these subjects are kind of taboo even in the most open minded culture. A first time virgin tester does their best, completes the job as their instincts tell them and from all the documentation (videos) they had learnt from. But they know there is more to it than just completing the task. In a stress free environment, the tester is enthusiastic and wants to give their best because the application deserves the best (in order to improve the product, make it bug free). So, they get the book  that contains all the various techniques for completing the task. They learn and apply all that they learnt. During the process they understand there is no way in hell they can go through some te