Software Testing HILARIOUS facts!

September 10, 2012 Kapil



The following jokes related to software testing have been compiled from forwarded emails and internet resources. Thanks to the ones who thought of them first.

Testing Definition
To tell somebody that he is wrong is called criticism. To do so officially is called testing.

Sign On Testers’ Doors
Do not disturb. Already disturbed!

Experience Counts

There was a software tester who had an exceptional gift for finding bugs. After serving his company for many years, he happily retired. Several years later, the company contacted him regarding a bug in a multi-million-dollar application which no one in the company was able to reproduce. They tried for many days to replicate the bug but without success.
 
In desperation, they called on the retired software tester and after much persuasion he reluctantly took the challenge.
   
He came to the company and started studying the application. Within an hour, he provided the exact steps to reproduce the problem and left. The bug was then fixed.

Later, the company received a bill for $50,000 from the software tester for his service. The company was stunned with the exorbitant bill for such a short duration of service and demanded an itemized accounting of his charges.

The software tester responded with the itemization:
  • Bug Report: $1
  • Knowing where to look: $49,999

Signs that you’re dating A Tester
  •  Your love letters get returned to you marked up with red ink, highlighting your grammar and spelling mistakes.
  • When you tell him that you won’t change something he has asked you to change, he’ll offer to allow you two other flaws in exchange for correcting this one.
  • When you ask him how you look in a dress, he’ll actually tell you.
  • When you give him the “It’s not you, it’s me” breakup line, he’ll agree with you and give the specifics.
  • He won’t help you change a broken light bulb because his job is simply to report and not to fix.
  • He’ll keep bringing up old problems that you’ve since resolved just to make sure that they’re truly gone.
  • In the bedroom, he keeps “probing” the incorrect “inputs”.


0

Quality or Quantity?

September 9, 2012 Kapil

Here is a widely told joke in the computer industry that goes like this: 

A man is flying in a small airplane and is lost in the clouds. He descends until he spots an office building and yells to a man in an open window, “Where am I?”
The man replies, “You are in an airplane about 100 feet above the ground.” The pilot immediately turns to the proper course, spots the airport, and lands. His astonished passenger asks how the pilot figured out which way to go. The pilot replies, “The answer the man gave me was completely correct and factual, yet it was no help whatsoever, so I knew immediately he was a software engineer who worked for Microsoft, and I know where Microsoft’s building is in relation to the airport.”

As long as information is in-formation (i.e. half-baked) it is to be considered as misleading piece of THIS (you may rearrange this) 

Besides just figures (such as Pass Fail Ratio aka ‘facts’), it is the job of the QAE to ensure the severity of the mathematics which is going to be ignored (i.e. fail ratio). It is not ‘how many’ failed it is - always – ‘which’ failed.

Understand of severity is synonymous with, yes, experience. And experience is the result of misunderstanding. Multiple times.

For QAE (Quality Assurance Engineers), focus ought to be quality and not quantity.

0

« Previous Posts Next posts »

Proudly powered by Kapil Saxena.