|
Testing Computer Software, 2nd Edition | 
 enlarge | Authors: Cem Kaner, Jack Falk, Hung Q. Nguyen
Publisher: Wiley
Category: Book
List Price: $65.00
Buy New: $23.98
You Save: $41.02 (63%)
New (17) Used (26) from $14.89
Rating:  36 reviews
Sales Rank: 17830
Media: Paperback
Edition: 2
Pages: 480
Number Of Items: 1
Shipping Weight (lbs): 1.1
Dimensions (in): 9 x 7.6 x 1.2
ISBN: 0471358460
Dewey Decimal Number: 005
EAN: 9780471358466
Publication Date: April 12, 1999
Availability: Usually ships in 24 hours
| |
| Also Available In:
|
| Similar Items:
|
| 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.
Product Description
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
|
| Customer Reviews: Read 31 more reviews...
 QA Must Have Tool June 18, 2008
Michele Smith (Maine)
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! December 3, 2007
Slavcho Ivanov (Sofia, Bulgaria)
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! November 30, 2007
Matthew D Edwards (Midwest USA)
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 July 23, 2007
A. Burtin (Chicago, IL)
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 May 13, 2007
Yegor Bugaenko (Moscow, Russia)
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.
|
|
|
. | |