Testing Computer Software, 2nd Edition [Paperback]

Cem Kaner (Author), Jack Falk (Author), Hung Q. Nguyen (Author)

Book Description

Publication Date: April 12, 1999 | ISBN-10: 0471358460 | ISBN-13: 978-0471358466 | Edition: 2

This book will teach you how to test computer software under real-world conditions. The authors have all been test managers and software development managers at well-known Silicon Valley software companies. Successful consumer software companies have learned how to produce high-quality products under tight time and budget constraints. The book explains the testing side of that success.

Who this book is for:
* Testers and Test Managers
* Project Managers-Understand the timeline, depth of investigation, and quality of communication to hold testers accountable for.
* Programmers-Gain insight into the sources of errors in your code, understand what tests your work will have to pass, and why testers do the things they do.
* Students-Train for an entry-level position in software development.

What you will learn:
* How to find important bugs quickly
* How to describe software errors clearly
* How to create a testing plan with a minimum of paperwork
* How to design and use a bug-tracking system
* Where testing fits in the product development process
* How to test products that will be translated into other languages
* How to test for compatibility with devices, such as printers
* What laws apply to software quality

Editorial Reviews

Amazon.com Review

The original printing of Testing Computer Software set the standard for the emerging field of test engineering with a full tour of the state of the art in managing the testing process. The reissued text makes this classic out-of-print text available once again. Though it relies heavily on older examples (including MS-DOS) and has not been updated, this text is still a worthwhile resource for practical-minded advice on the realities of testing.

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.

Review

"I enjoyed reading Testing computer software. The text contains numerous highlights Offering practical advice, authoritative figures you can cite to customers and higher management, and entertaining anecdotes to share with coworkers Although some sections need updating, I still think it is a valuable training and reference source for software testers, managers, and developers." --Diomidis Spinellis; IEEE software magazine (May /June 2001))

"Deep insight and a great deal of experience is contained in this book" (Database & Network Journal, Vol 30/5 2000)

See all Editorial Reviews

Product Details

• Paperback: 480 pages
• Publisher: Wiley; 2 edition (April 12, 1999)
• Language: English
• ISBN-10: 0471358460
• ISBN-13: 978-0471358466
• Product Dimensions: 7.5 x 1.1 x 9.2 inches
• Shipping Weight: 1 pounds (View shipping rates and policies)
• Average Customer Review: 4.2 out of 5 stars  See all reviews (54 customer reviews)
• Amazon Best Sellers Rank: #33,965 in Books (See Top 100 in Books)
  • #14 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Testing
  • #49 in Books > Computers & Technology > Computer Science > Software Engineering

Most Helpful Customer Reviews

58 of 59 people found the following review helpful

5.0 out of 5 stars Testing Computer Software is one of those rare CompSci Books October 5, 1999

By Erick M. Griffin

Format:Paperback

Testing Computer Software is one of the those rare books that has taken on the problems of the Verification Engineer. As all of us know, most books written today are targeted for the development audience and even many of these are either poorly written or try to cover too much area. This book however, though broad in its scope, does a good job of treating all of the important areas in verification and testing.

I have found Chapters 2, 3, 7, 11 and 12 to be the most useful and poignant to the average engineer. Not only is each chapter well laid out, but the authors also offer compelling arguments in each chapter to back up their arguments as well. I enjoyed particularly Chapter 3 the section on Path Testing, which conjures up horror stories from my development days. In this section the authors assert that 100% path testing does not imply 100% test coverage. They go on to argue with some rigor why the two are not necessarily the same. Many of you as I can probably claim that though all of the paths in their code were tested, verification was still able to find some condition that would make some part of the code fail. This chapter explains why this may be so and methodologies on how to attack testing those areas.

You will find the book well structured, informative and actually intuitive to navigate through. Each chapter builds on the previous chapters to provide the engineer with a clear idea of all the steps and intricacies involved in testing and verifying complex programs. It can therefore be used by the beginner as a source book for specific test applications, or by the team lead or manager who needs to know more about the actual scope and planning of a complex testing project. This book surely fills a great void in the area of publications software verification.

36 of 38 people found the following review helpful

5.0 out of 5 stars If you read only one book on software testing, read this August 13, 2001

By Bret Pettichord

Format:Paperback

This book should sit on the desk of every software tester.

Many books will tell you how to test when you have enough time and cooperation. This book tells you what to do when the schedule is tight, the specification is missing, and the developers are tired of your focus on problems. It has sound advice and is a pleasure to read. I keep coming back to it. Feel like you have an impossible job? Read this book.

(Note: this book was published in 1993 and has not been updated since then. Wiley lists 1999 as the publication date because that was when they became the new publisher for the book, which is destined to become a classic.)

24 of 24 people found the following review helpful

5.0 out of 5 stars Excellent orientation for new test professionals July 7, 2004

By Mike Tarrani HALL OF FAMETOP 500 REVIEWER

Format:Paperback|Amazon Verified Purchase

When I first read this book over eight years ago I was less than enthusiastic. At the time I felt that the approach was not rigorous enough. Over time I came to appreciate the pragmatism and how the approach in this book reflects the realities of software testing instead of a rigid, purist view as an unattainable ideal.

Everything the new or intermediate test professional needs to know is covered. The practices and techniques provided will foster sound QA practices and will step you through developing test strategies, and from those, developing and executing test cases. These are the real essence of testing, and this book covers them exceptionally well.

I like the coverage of testing systems and artifacts that are not software - documentation, hardware, and localization testing advice shows that testing is not limited to software. As importantly, the chapter on legal consequences of software defects will show testing in a perspective that is often overlooked, even by seasoned test professionals.

If you are new to software testing, or have some experience, but no formal training, this book will provide you with the right way to approach software testing, and will give insights that would take years to learn on your own.