 | |
| |
Surviving the Top Ten Challenges of Software Testing: A People-Oriented Approach
 |
Author: William E. Perry, Randall W. Rice
List Price: $27.95
Our Price: Click to see the latest and low price
ISBN: 0932633382
Publisher: Dorset House (October, 1997)
Edition: Paperback
Sales Rank: 33,138
Average Customer Rating: 4.17 out of 5
|
Customer ReviewsRating: 5 out of 5
Excellent review of the daily pitfalls of software testing
This is an excellent review of the biggest recurring problems of the software testing world. As I read the descriptions of each of the 10 challenges, I was astonished at how many of the pitfalls I fall into on a regular basis. Perry & Rice don't just lay out what the challenges are - they also discuss how to meet each one. Each item on the list has its own chapter with sections on the impact on testing, solutions to the challenge, impediments to implementing the solutions, and helpful guidelines to creating a plan of action. This is without a doubt an excellent book for those of us in the trenches of software testing each day. (One bit of advice, though - if you're looking for a book on "how to do software testing", look elsewhere. Perry and Rice have other good books on the subject, but this one is really intended to help you step back from your daily testing work and see where you could improve on your approach to it.)
Rating: 4 out of 5
Bringing testing out of the closet
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.
Rating: 1 out of 5
Not worth my time
The industry has long since passed Perry by. I found this book simplistic in its approach, mired in problems that most software development houses solved long ago, and dependent on overblown methods no longer appropriate in the internet age. As for the question of how to influence, Weinberg is a far better guide. As a test manager, I would recommend almost any other book on testing to members of my staff.
Similar Products
· Black-Box Testing : Techniques for Functional Testing of Software and Systems
· Lessons Learned in Software Testing
· Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing, 2nd Edition
| | | | | |
| |
