Customer Reviews
IMO Hetzel is better - By: Gareth Greenwood, 09 Jun 2008 
Having often to advise clients on testing high-integrity systems, I have a list of books that I tend to recommend to them. I bought this text by Black to see whether I should add it to the list. I decided that I probably wouldn't - & certainly wouldn't for British clients.
Some American authors clearly have no idea of the degree to which their style can sound crassly uneducated to British readers. Most of the time one can read through it but I found Black's style the most irritating I've encounteredin many years. IMO his description of what is good & poor stylein bug reports applies ironically to his own writing! Setting aesthetic sensibilities aside, however, I wasn't much impressed by the overall approach either.
While it is reasonable for a book on software testing managment to adopt a pragmatic experienced-based approach, it is IMO a disservice to readers not to indicate where & how practical approaches are supported by the underlying theory of coverage-based testing. Black, however, omits this entirely. In particular he gives no real guidance on how to select appropriate coverage domains according to the criticality of the tested system. A further consequence is that the book fails to relate what it recommends to the provisions of the increasing number of international standards for software processes - particularly those intended for high-integrity systems development.
One thing I thought particularly bad was Black's view of the people-management side of testing. At one point he suggests that test reports should not "make individuals look bad". Having worked on SIL4 developments with engineers who clearly hadn't a clue, I beg to differ. IMO product safety assurance trumps any number of bruised tester egos. I'd sooner offend the great unwashed than have a highly safety-critical product go out of the door after inadequate testing.
On the positive side, there are many nuggets of wisdom to be found if you're prepared to wade through the verbiage. I think the book is sound enough for run-of-the-mill testing of non-critical systems. I wouldn't, however, use Black's approach to software test management on SIL3 or SIL4 systems. IMO Hetzel's approach is better if only because it contains less that you might judiciously choose to ignore.
In summary, a pretty disappointing book.
Excellent advise. - By: colinmee@purplenet.co.uk, 20 Sep 1999 
As a test manager working on my fourth testing project I can honestly say that I wish I'd read this book before my first one. I was thrownin at the deep end when the test manager was sacked & I had to step in. This book confirms that most of the things we did were right & also highlights the things that can go wrong, particularlyin the 'soft' issues. It's especially good on the managerial aspects & politics of testing & I recognise quite a few of the political mistakes that test managers can make.
As a review of testing techniques its not so hot but the title 'Managing the Testing Process' says it all. Its about managing & it does it very well.
Good, but not great - By: , 20 Jul 1999 As an aspiring tester, I can say that this book is not quite what I was looking for. It didn't give me a big picture of the testing process, nor did it give me any insight into how to use effective methods. On the whole, the better book for your money is "Testing Computer Software" by Kaner, et al. Now that one is a winner. This, just so so.
Great Book!!! - By: , 16 Jul 1999 
In theory, practice works 100% of the time. In practice, theory do not always works . This book has the "proven testing theory & testing practice"
I do recommend it highly!
Simply Great! - By: , 15 Jul 1999 Very clear writing, a great voice offering light & granular guidance, & the CD is helpful to those who might need a "jump-start" to managing their own testing strategy & process.
Why not 5 stars: I wished the CD had been more robust, & that a website/extranet for the book could be includedin the purchase price.
