Testing Computer Software, 2nd Edition 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you grow your business. Learn more about the program.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Frequently bought together
Customers who viewed this item also viewed
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.
"Deep insight and a great deal of experience is contained in this book" (Database & Network Journal, Vol 30/5 2000)
There was a problem filtering reviews right now. Please try again later.
One note though, pick your vendor wisely. I bought this used in "good" condition with "some notes and highlighting." Well..I haven't really noticed much highlighting because I've been so preoccupied with keeping the pages together! My book came completely un-bound for the first 60-70 pages, which subsequently led to the remainder of the book coming apart too. No matter how carefully (read-Uncomfortably and Awkwardly) I used it. UNACCEPTABLE
What's even more irksome, is that this is more so a textbook--something I would like to be able to refer to every now and then..
Guess I'll just have to buy another NEW copy now..
My advice--be careful about buyng USED books online. And just steer clear entirely when the books you'll be byung are reference/text-books.
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.
I haven't finished the book yet, but here's what I like
- Information is simply written and easy to understand so far. Not all text books do that and I appreciate when it is.
- This book isn't just geared to the subject matter experts or even people new to the subject. The preface addresses this and offers suggestions
- Each chapter starts by the writers telling you why that section is necessary, a brief summary and sometimes even outside references to follow up with.
The only bad thing I can say so far about this book is that there doesn't seem to be any updated versions. While I'm assuming that methodology doesn't really change, the book is already ten years old. I'm hoping that my opinions don't change as I get more in-depth, but if they do I'll come back and update this review.
This book was recommended to me by my test lead from Satisfice
It presents very useful information in a refreshing style thatallows you to apply it to your testing immediatly.
Anyone who wantsto improve their thinking process should purchase this book, no matterhow little or how much experience you have this book is worth having:)
I look forward to reading other books by Cem and crew.
Top international reviews
As someone doing a course in software development, I was hoping for a book that explained all different types of testing, how to carry out these tests and how to document the tests. While this book achieved some of that, much of its content was not suited to me and it was sometimes hard to find what I was looking for. Another problem I had with the book was that it was very dated with the examples it used.
My recommendation would be only get this book if you are involved in QA.
Large portions of the book constantly refer to driving hardware devices (e.g. handling keyboard input, refreshing the screen in error recovery procedures, observing the [text] console while it's being updated in order to spot any irregularities, and one of the tips given is that if the screen is updated too quickly for you to be able to see an irregularity you should try running the program on a slower computer!)
Is it necessary to advise the reader about the design of a bug tracking system? (there are so many commercial and even free products available). Once again there is useful information in this chapter - you just need to apply it in *selecting* one of the available bug tracking systems.
If you're willing to put in some hard work [distilling the principles] then you might get something out of this book, but for most people my advice would be to give this one a miss.