Friday, 7 June 2013

“Convivial way to understand software testing”




Who is Software tester…..???

Officially a person who conducts prescribed tests on software programs and applications prior to their implementation to ensure quality, design integrity and proper functionality. They apply rigorous testing methods including extensive end-user simulations to uncover program "bugs" which are then eliminated by the software programmers.”

But how people other than testers understand it??

A person who always criticise the work done and always brings a bad news and to do so officially is called software test engineer.

Tester’s perspective!!!

A glass is half filled then
To an optimist, the glass is half full.
To a pessimist, the glass is half empty.
To a good tester, the glass is twice as big as it needs to be.

Who drives a testing process???

A drunken driver is very dangerous. So is a drunken backseat driver, if he’s persuasive!
'Dude, make a left.'
'But those are trees…!'
'Trust me...'“

Essential operational decisions are made by someone else (project manager, product owner, whatever you call him). But if we are not the drivers, our position is certainly close to this of a backseat driver, we have our maps, good knowledge of the area and our experience, and we give advice that is used to take real decisions. So don’t be a drunken backseat driver, its dangerous! If you are inebriated by an obsessive desire to fix a bug, or by any thing else you’ll be taking your company directly into the trees. And, as with any drunk person… Whenever your judgment isn’t objective… At least recognize that you may be drunk! Will make it easier for everyone else.


Where to find a bug?

Under a streetlight, on a very dark night, a software tester was looking for a set of lost keys.A policeman came by, asked him about the object of his search, and joined him to help. After the two had searched for some time, the policeman asked,

“Are you sure you lost them here?”
“Oh, no,” said the software tester. “I lost the keys somewhere else.”
“Then why are you looking for them over here?” the policeman asked.
“Because this is where the light is!” the software tester replied.
Moral: Do not be so stupid that you search for bugs only at the obvious places.

What is software testing intended to?

To deduct number of bugs possible and build confidence on the product….but testers tends to loose confidence if they don’t find bugs in the project…!!!

Suggested easier way ……..but understood as a wrong way !!!

A group of managers were given the assignment of measuring the height of a flagpole. So they go out to the flagpole with ladders and tape measures and they’re struggling to get the correct measurement dropping the tape measures and falling off the ladders.
A tester comes along and sees what they’re trying to do, walks over, pulls down the flagpole, lays it flat, measures it from end to end, gives the measurement to one of the managers and walks away. After the tester is gone, one manager turns to another and laughs,
“Isn’t that just like a tester?
We’re looking for the height and he gives us the length.”

Will certification make you an expert!!!

“I used to play sports... Then I realized you can buy trophies. Now I'm good at everything!“

A plaque, a crown, a card, a trophy… They prove you’ve mastered a skill. Trophies are nice and great, but only if they are accompanied by skills and real world practice. Trophies that can be attained without these traits are just empty cups.

One should beware when dealing with “achievement symbols”. At times, acquiring the symbol does not mean acquiring the achievement or skill too!

For example, just as buying the trophy doesn’t make you good at sports,
Similarly getting a testing certification won’t make a tester good at testing… The certifications syllabi try to teach only specific lexicon and terms definition, but not the real practice of testing, because they don’t/can’t cover the interactions between persons and players.
For some people, the joke could be read as “I used to practice and study... Then I realized you can pass a certification. Now I can prove mastership - without the effort of gaining it!” Be sure to be from the ones who keep learning and carrying the skill.

Understand how much to test….!!

In a car manufacturing company a person with no formal experience was appointed as an observer on the production line. His work was to check whether the painted doors have an even coat on it. The next day there is a knock at the Personnel Manager’s door. The Foreman throws open the door and begins to rant about the new employee. He complains that he is incredibly slow and the whole line is delayed, putting the entire production line behind schedule.
The Personnel Manager decides he should see this for himself, so the two men march down to the factory floor. When they get there the line is so backed up that there are doors all piling up. At the end of the line stands a nervous new employee.
The personnel manager observed the he was examining each door inch by inch by slowly gliding the tool all over the door…..

Summary:

A software test engineer must have a clear idea about what is testing, the role of a tester, the need/purpose of the testing, how to test and how much to test, what to test and where to test.
“The business of the company depends on the quality of their product….and for the quality the company depends on the TESTER”….so be proud to be a tester.

Post by :- Surya Prakash Goske

Published By :- Pardha Saradhi
-



1 comment:

  1. Good article Prakash. useful information. Keep posting .

    - Pardha Saradhi

    ReplyDelete