Anecdotes related to Software Testing

The jester testers 1

jokes about software testers and software testing

Question: How many software testers does it take to change a light bulb?

Answer: None. Software testers just noticed that the room was dark. Testers don't fix the problems, they just find them.

Question: How many programmers does it take to change a light bulb?

Answer: What's the problem? The bulb at my desk works fine!

Q: How many programmers does it take to change a lightbulb?

A: NONE! That's a hardware problem....

Question: How many internet marketers does it takes to change a lightbulb?

Answer: They'll reveal the answer to you in a $47 ebook..

One developer to spend five minutes implementing ChangeLightBulbWindowHandleEx.

One program manager (PM) to write the specification.

One localization expert to review the specification for localizability issues.

One usability expert to review the specification for accessibility and usability issues.

At least one dev, one tester, and one PM to brainstorm security vulnerabilities.

One PM to add the security model to the specification. 136 The Best Software Writing I 2. Dev = developer = an actual computer programmer – Ed.

One tester to write the test plan.

One test lead to update the test schedule.

One tester to write the test cases and add them to the nightly automation.

Three or four testers to participate in an ad hoc bug bash.

One technical writer to write the documentation.

One technical reviewer to proofread the documentation.

One copy editor to proofread the documentation.

One documentation manager to integrate the new documentation into the existing body of text, update tables of contents, indexes, etc.

Twenty-five translators to translate the documentation and error messages into all the languages supported by Windows. The managers for the translators live in Ireland (European languages) and Japan (Asian languages), which are both severely time-shifted from Redmond,3 so dealing with them can be a fairly complex logistical problem.