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.

Comments

Post a Comment

Popular posts from this blog

A Testers Life

-
Image
There is a plethora of examples explaining about a Developer's life. It is time to show the QA in the same "light". I am a QA and only some of these are my experiences. Which ones can you relate to? This is what they think QA are like This is what we wish QA could be like My first day on the job - I am introduced. Product training for QA I am trying to find my way through SharePoint It has always been like this. It's not a bug, don't log a ticket for it, the existing QA tell me. (Or maybe they do not want to admit that they missed a big fucking bug.) This is how Devs are trained about the project. This is how QAs are trained about the project I finally get my build to test. It is 5:00 pm Friday I am not given access to anything, but I am expected to test Setting up Test Data Smoke Testing (it usually never detects the fire or smoke till we get to production and a customer reports it. But it sounds good.) Trying to
Read more

Lots of Work

-
Image
“Working so hard” “There is a lot of work to do” “Such a big application” “So many bugs”  "Too much work load"  "Not enough time" What should it really mean to the person hearing it? – Nothing. I have seen members take loads of work and not bat an eye and do it with ease. I have also seen members take little work and make it look big and stress out and stress others out. I have also seen organizations that plan and work smart. I have seen organizations that plan to work really, really hard. I am not here to explain the right way of doing things. Whatever floats your boat!! Lol But, when people talk about a lot of work, it reminds me of the Woody Allen movie – Annie Hall There is a scene in the movie with a psychiatrist. The conversation goes like this - Alvy's psychiatrist : How often do you sleep together? Annie's psychiatrist : Do you have sex often? Alvy Singer : Hardly ever. Maybe three times a week.
Read more

Vanilla Ice Cream caused General motors to not start

-
Vanilla Ice Cream that puzzled General motors’!!!! An Interesting Story Never underestimate your Clients' Complaint, no matter how funny it might seem! This is a real story that happened between the customer of General Motors and its Customer-Care Executive. Pls read on..... A complaint was received by the Pontiac Division of General Motors: 'This is the second time I have written to you, and I don't blame you for not answering me, because I sounded crazy, but it is a fact that we have a tradition in our family of Ice-Cream for dessert after dinner each night, but the kind of ice cream varies so, every night, after we've eaten, the whole family votes on which kind of ice cream we should have and I drive down to the store to get it. It's also a fact that I recently purchased a new Pontiac and since then my trips to the store have created a problem..... You see, every time I buy a vanilla ice-cream, when I start back from the store my car won
Read more