Book: Perfect Software, illusions of testing 7 Years, 3 Months ago
This is an interesting book on big picture questions like understanding (and being able to explain to management) what software testing can and can't accomplish, why perfection is never possible, and how much energy to put into chasing some approximation of perfect software.
Weinberg is a good, perceptive, and entertaining writer. I remember reading his Secrets of Consulting many years ago. As another reviewer noted
QUOTE: If you are looking for a "how to" book, you should look elsewhere. If you are looking for a "why" (and sometimes "why not") book, this might be for you.
Here's a sample from the publicity materials.
QUOTE: The job of software testing, we know, is to provide
information about the quality of a product. Many people
believe that the only way to get such information is
to execute the software on computers, or at least to
review code. But such a belief is extremely limiting.
Why? There’s always other information about product
quality just lying around for the taking—but only by
managers who are watching, and who recognize it as
relevant. . . .
Consider the following from Dani Weinberg
about one of her consulting experiences in the dogtraining
world: “A woman with a sheltie puppy was at
her wits’ end because ‘he always poops on the livingroom
rug.’ She loved the little guy, so before giving
up and taking him to the Humane Society, she came to
me for a consultation. I listened to the woman
describe the problem, then asked, ‘Are there any other
“The woman thought for a while, then said, ‘Well,
yes, there is one. He has this annoying habit of
scratching on the front door and whining.’”
It’s easy to laugh at someone else’s inability to see
the connection between two “problems,” but that sort
of blindness is typical of people who are too close, too
emotionally involved with a situation. Learning to recognize
free information is one of the secrets of successful
Re:Book: Perfect Software, illusions of testing 7 Years, 3 Months ago
I think testing should be part of an overall Quality Control program within an organization which encourages all those involved in product development process to help define and measure its success. It is amazing how often I experience the "throw it up and see if it sticks" mentality when it comes to application development, new product development, etc. When you take this course of action without proper planning and key metric measurements we rely on the end user to test our products which is just not fair to them.