Testing Jokes / Recent Jokes

People for Ethical Treatment of Software (PETS) announced today
that more software companies have been added to the group's "watch list"
of companies that regularly practice software testing. "There is no
need for software to be mistreated in this way so that companies like
these can market new products," said Ken Grandola, spokesperson for
PETS. "Alternative methods of testing these products are available."
According to PETS, these companies force software to undergo
lenghty and arduous tests, often without rest, for hours or days at a
time. Employees are assigned to "break" the software by any means
necessary, and inside sources report that they often joke about
"torturing" the software.
"It's no joke," said Grandola. "Innocent programs, from the day
they are compiled, are cooped up in tiny rooms and "crashed" for hours
on end. They spend their whole lives more...

Manufactured by: MOMCATT - Makers Of Many CATTs
Anytown USA (Offices around the World)

FEATURES

Low Power CPU
Self Portable Operation
Dual Video Inputs
Dual Audio Inputs
Audio Output
Main Input Multiplexed with Error Output
Auto Search for Input Data
Auto Search for Output Bin
Auto Learn Program in ROM
Auto Sleep When Not in Use
Wide Operating Temperature Range
Self Cleaning

Production Details

After basic construction, the unit undergoes 6 weeks of ROM
programming and burn-in testing. MOMCATT will typically reject
inferior products, but sometimes people will salvage rejected units.

These factory seconds may or may not perform the same as units that
pass the standard acceptance testing. All of the previously listed
features are installed during this interval. Since MOMCATT uses many
different suppliers, there is wide variation between the more...

I think animal testing is a terrible idea; they get all nervous and give the wrong answers. — Peter Kaye

Programmer produces code he believes is bug-free.
Product is tested. 20 bugs are found.
Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
Repeat three times steps 3 and 4.
Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
Users find 137 new bugs.
Original programmer, having cashed his royalty check, is nowhere to be found.
Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
Original programmer sends underpaid testing department a postcard from Fiji.
Entire testing department quits.
Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
New CEO is brought in by board of directors. He more...

CIA Affirmative Action
A few months ago, there was an opening with the CIA for an assassin. These highly classified positions are hard to fill, and there's a lot of testing and background checks involved before you can even be considered for the position.
After sending some applicants through the background checks, Training and testing, they narrowed the possible choices down to 2 men and a woman, but only one position was available.
The day came for the final test to see which person would get the extremely secretive job. The CIA men administering the test took one of the men to a large metal door and handed him a gun. "We must know that you will follow your instructions no matter what the circumstances", they explained.
"Inside this room, you will find your wife sitting in a chair.
Take this gun and kill her.
"The man got a shocked look on his face and said "You can't be serious! I could never shoot my own more...

The Life Cycle of Software

Programmer produces code he believes is bug-free. Product is tested. 20 bugs are found. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs. Testing department finds that five of the fixes didn't work and discovers 15 new bugs. See 3. See 4. See 5. See 6. See 7. See 8. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released. Users find 137 new bugs. Original programmer, having cashed his royalty check, is nowhere to be found. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs. New CEO is brought in by board of directors. He hires programmer more...

While we believe we will be fully Y2K compliant by January 1, 2000, and most of our subsidiary units and contractors claim they will also be fully compliant, we obviously need to make some preparations in case unexpected challenges impair our ability to meet the needs of our customers.
Enclosed with this memo is a "Y2K Backup System" device designed to meet short time emergency needs in case of a computer operations failure, or operational delay. This device is the company's Primary Emergency Network Computer Interface Liaison device (P.E.N.C.I.L.).
This device has been field tested extensively, including certification testing, as well as volume and stress testing. Properly maintained, the device meets all the requirements for coding and data input. Prior to use, the (P.E.N.C.I.L.) will require preparation and testing. Tools and supplies required will be: A sharpened knife or grinding device;and a supply of computer paper (with or without holes).
Gripping the more...