Tool is only as good as the user

As a SDET, I believe that the automation tools wrongly called testing tools, can do no testing. It is a tool that does what I tell it to do. I can tell it to go through all the pages and it will. I can tell it to pass a failed test and it will pass. I can tell it to fail the whole application and it will fail. Once again, it is a tool that does what I tell it to do.



Kind of like this story - 
Once upon a time there was a King who owned a device that worked like a lie detector. The device had a pointer that would point to the left when a person wearing it lied, and to the right when the person spoke the truth. The king was very happy that he found a device that will help him in judging people rightfully. The minister was concerned though. He did not believe the device was of such great use. He also feared, if would cause harm in certain cases.

One day the cops brought in a farmer who killed his landlord.  The cops put the device ("lie detector") around the farmer's throat and asked him if had committed the crime. The farmer replied "No". The device pointed to the right, which meant the farmer was telling the truth. The cops released the farmer. But the village folk complained again that they had witnessed the crime.

So, this case went to the King and the minister, where the farmer was asked the same question and the device pointed to the right upon the farmers answer. The King tried the device on himself and lied while wearing it and the device pointed to the left. This got the King confused. The minister stepped in and asked the farmer if had 'indeed killed the landlord?'. To which the farmer replied, "Yes". The device pointed to the right again.

The farmer killed someone, but he did not consider it a crime. So, that explains why the machine reacted the way it did. The machine did its job.


Tools will always be tools. Tools are only as good as the user. To find answers, we have to ask the right questions. To find bugs, we have to ask the right questions. Too many questions or less questions are not the key here. The right question in the right context matters. Even when using Google search or queering data base tables, testing an application, it is our responsibility to choose the words / questions / tests wisely.

If testing was like sex

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 techniques, due to lack of time or lack of more knowledge or it just does not make sense.

In a stressful environment, the tester does not dare to attempt more than what is expected. The job is complete and that is all that matters. They do not have the luxury of knowing the application more. Besides no on ever got fired for missing a bug.

In a perfect environment, the tester does not just jump in to finish the task. They get to know the application. The more they understand the application, the better they can plan their tests. They may be the one or they may not be the one. They wont know more till they explore.

A knowledgeable tester will realize it is the best thing to step down if they are not equipped to test the product.
An intelligent tester will train themselves to gain the knowledge necessary to test the product.
An average tester will just hang in there and look busy while doing their best.

A tester that takes the time to learn about the application and takes the time to explore it can come up with the best possible tests suitable for the particular application. Every application is unique with certain similarities. They may all look the same but they come from different places. Their needs are different. Their environments are different. They are made differently. They are made with sugar and spice and everything nice. (lol)

Do not assume your application is your female dog. Know your application accept it with all its flaws and respect it. Then custom design your tests. Never stop exploring. There is no stopping you now.