Testing has often been the misbegotten portion of the software development process. Frequently neglected until the semi-chaotic end of the production cycle, the testing phase has traditionally been shortened to accommodate a fixed release date. The relationships between the developer and test groups are to some extent adversarial, but in so many cases it often breaks down into open hostility. Among developers, it is often considered demeaning to have to soil ones hands by actually testing the code. With such a sullied background, it is no wonder that production code is generally riddled with bugs. As the authors of this book point out, all of the above are dangerous conditions. With the expansion of code reuse and RAD tools, the development of the initial iteration is going to be done at a faster pace than before. Since the number of pathways through the code is operationally infinite, the only way relatively bug-free code will be developed is by allocating more resources to testing and making the choice and tracking of test cases a more scientific endeavor. The most significant point of the ten made in this book is that the testing process should be considered on an equal basis with that of development so that both groups communicate as equals. Without that, all the fancy, efficient tools in the world are reduced to the level of mere toys. This is a book that can and should be read by developers, managers and yes, even testers, as all will benefit from the simple words of wisdom.
When this book was written software testing was starting to consolidate into an 'honorable' profession, and the number of good books about testing could be counted on your fingers (and probably a few toes). The discipline has matured into a profession, and there are so many excellent books on the subject now that it boggles my mind. You'd think that the top ten challenges listed in this book would have been long ago resolved and replaced with a new set. Sadly, that isn't the case. Each challenge … more
Charlie Ashbacher is a compulsive reader and writer about many subjects. His prime areas of expertise are in mathematics and computers where he has taught every course in the mathematics and computer … more
Consider the Source
Use Trust Points to see how much you can rely on this review.
The software field has more than its fair share of survival titles. Survival books help us survive harsh deadlines, endure unsupportive bosses, improve poor software processes, suffer inadequate specifications, and stay in line during death marches. The software field is bleak indeed. --Doug Nickerson, Dr. Dobb's Electronic Review of Computer Books -- Dr. Dobb's Electronic Review of Computer Books