Summaries and Customer Reviews are supplied by Amazon.com

The best thing about Testing Computer Software is its practical point-by-point guide to everyday software testing, from creating a test plan, to writing effective bug reports, to working with programming staff and management to fix bugs.

That said, this book's early frame of reference shows how far we've come. (The book relies heavily on MS-DOS examples and features some truly embarrassing anachronisms, including the mention of testing dot-matrix printers and even EGA/VGA video modes.) The bibliography stops at sources from 1992 and features many references from the 1980s. Nowadays, automated software testing tools are the staple of any testing strategy. This book even advocates a wait-and-see approach to the "new" Microsoft Test.

These limitations aside, there is still a good deal to mine here. Much of the approach to testing is still very valid for any aspiring or working test engineer. Clearly, readers of the first edition will have little reason to upgrade to this second edition, but for anyone who appreciates a "classic" (and indeed a pioneering) text in the field of software testing, it's good to have Testing Computer Software in print again. --Richard Dragan

Topics covered: test case design, test planning, project lifecycle overview, software errors, boundary conditions, bug reports, regression testing, black box testing, software quality and reliability, managing test teams, printer testing, internationalization, and managing legal risk.

Average Customer Rating:

QA Must Have Tool	Customer Rating:
The QA department where I work already has one of these books, which I actually read cover to cover a ways back. I decided to get one for myself to keep as a handy reference when I am not physically on the job, but thinking of it and planning out my testing. This is a must have for anyone in or interested in the QA/Software Testing field.

Just what I needed!

Customer Rating:

I was trying to become a better project manager in our small and new software firm. We had lots of problems, and especially with the QA of our product. This book helped me (and still does) understand the approach and the idea of testing software. We managed to greatly improve the quality assurance process. Even before this book I knew testing is fundamental to the software development, but now I now "why" and most important "how".

Practical, fundamental and necessary reading!

Customer Rating:

Practical software testing from practicing software testers. Much of the time, books are written with an attempt for the author to launch some new iteration of their career and so forth thereby confusing the application, message and usefulness of the book in question. This book is very simple. It discusses, problem, approach, solution, experience and commentary. Though never as wonderful as being mentored first-hand by an expert, this book is practical enough to leave you with near first-hand experience of how to think through 'what to test', 'how', 'to what extent', etc. No book will solve your testing problem. This book simply takes you on the path of though evolution towards doing such.

QA Specialist	Customer Rating:
The book was very helpful for me as a beginning QA Specialist. I would recommend it for background and foundational info.

Good, but very old

Customer Rating:

I think that Cem Kaner's book was perfect 20 years ago. Right now it's very funny in most chapters. For example we have a whole chapter for printer testing. I don't think that more than 1% of programmers are working now directly with hardware. Also, we have many examples for computers with 640Kb or RAM. Many examples and test types are expired. I was confused why editors didn't remove them or change. Anyway, I recommend to read it as an overview. Moreover, this book is more like reference, not a book for reading. So, buy it and have in your library.