Summaries and Customer Reviews are supplied by Amazon.com

Average Customer Rating:

great book	Customer Rating:
I saw this book in my public library, and after reading it once i figured out that i can't stay without it! so i decided to buy it, because you will always find a situation where this book can help you to plan testing processes or manage an existing process. Either if you are a software tester or a lead/manager this book can help a lot; highly reccomended!

IT 645 College Book Review	Customer Rating:
This book does not go well with the class, I would suggest to any university that is using this book for IT 645 class, to find a different author.

Straight forward guide to test management

Customer Rating:

"Managing the Testing Process" is the book that I used as a guide when I started as a tester years ago. I found that, while it focuses on the bigger picture of test management, many of the tidbits included help me to report what I do to non-testers. It may seem simplistic to use tools like Excel or Access to capture and report information. However, I have worked at companies that didn't want to lay out any cash for testing and testing tools. But what comes installed on most corporate desktops? Excel and Access! They are tools that are easily used and readily available for capturing metrics and generating reports. Metrics and reports are the mainstay of the testing community and demonstrate to others that testing is a critical component of the software development process. I have recently returned to using some of Rex's reports to highlight the problems that exist in my own projects. Everywhere I have worked there seems to be a common theme that producing quality software is difficult, yet Rex's methods for collecting and reporting project statistics give the most bang for the buck when dealing with people who don't want to understand technical issues or read lengthy documents on the status of a software project. If you are just setting up a test organization, or are new to testing yourself, this book provides everything you need in order to cover the basics. I also recommend "Managing the Testing Process" to testers just getting their feet wet, even if they're not managing a test team. This book demonstrates why testing is important and gives a good "big-picture" understanding of the artifacts that a test team should be producing.

Rex Black explains clearly and deliberately

Customer Rating:

My take on this book is that it`s more about creating organization within your test schedule and documentation. He goes through each step of the QA process, from documenting requirements to double-checking the results, and explains how you can spend hours upon hours of documentation for your QA efforts. It`s useful if you have nowhere to start. It`s full of new ideas if you already have a system in place. It can help you get more out of your testing organization if you have your QA manager read it for homework.

Testcase Tracking in Excel?

Customer Rating:

Black keeps on stating, that he has a lot of practical experience. The book is supposed to help me in my daily business as a (for me) testmanager. Well, it did not. 1) I can not take him serious (watching him give a presentation is fun and interesting, though), when he proposes to manage testcases in Excel. Of course I tried that (didn't we all try that once?), in fact have seen it on several projects. It failed every single time. You need a database system for even medium sized projects. I actually found it very helpful to use a bugzilla like system to manage them. 2) He describes a bug tracking system. That might have been necessary a few years ago, but today there is Bugzilla (or Jira, or the like). They are cheap, very flexible and developed from a need. On the World Congress for Computer Quality in Munich (2005) I talked to several vendors of such testcase tracking systems. They were quite expensive and none could provide me some of the feautures possible with Bugzilla. Oh, they had all kinds of fancy wizards and automatic equivalent classes generators and the like. Too bad, that I never missed those things, might be because time is the single most contraining factor for me and my team. So, the book gives a good theoretical overview. It is easy to read and beginners will certainly learn something from it. If you have any background book on testing and have some experience in testing, don't bother.