<< 1 >>
Rating: 
Summary: not all that
Review: i find the book too advance to understand
Rating: 
Summary: Unreadable
Review: I read the first chapter, and am tempted to throw the book out. The author cannot write a clear English sentence to save his life.
Rating:
Summary: Move Away from this Page
Review: The book is full of hypothesis. Till now nobody would have implemented all the checklists/templates/procedures mentioned in this book, in their real environment and I can bet on this.Checklists are needed if the task of review/testing is very critical and the organizational processes shall demand that. An attempt to define a checklist/template to make it global is real childishness. The definition of Verification and Validation itself is written wrong in this book. I dont know if these terms had such definitions during the past years. Summary: We are in 2003 now. If somebody wants to go back to 1970 then this book will be very useful for them. A wise decision for normal readers would be to move away from this page. Thanks.
Rating: 
Summary: Solid basics, but needs to be updated
Review: The Perry text will serve as a solid basic text for academic settings (thus the 4 star rating) but needs to be updated for client/server testing situations.
Rating:
Summary: Fails the readability tests
Review: There are a few things to say in favour of this book:
1. It does walk through on how to approach testing in your organization (however, it is definitely oriented towards organizations with established testing principles).
2. It does give you some background information on software testing. Sadly, these are mainly explained in a textbook like manner, making them hard to digest.
3. It provides a thorough, detailed and tested methodology for software testing throughout the various life cycles. Yet again, due to the book's textbook like manners, I found it hard to actually implement the offered methodologies. Whatever positive attributes the book has to offer, they pale in comparison to the book's negative aspects:
1. Total unreadability: The book written in such a boring manner, you will find yourself reading every page thrice, and still lack the satisfaction of being able to quote the meaning of what you just read.
2. Lack structure: Paragraphs are thrown in one after the other; it's hard to decipher what leads where.
3. Repetitiveness: Items like "building the test plan" repeat themselves for no particular reason.
4. No examples: It's hard for the text to find any foundation in your mind when there are no examples to help the reader relate to. Given its monotonous descriptions, nothing could hinder the reader's efforts to understand and implement the book's ideas more than that. The final verdict: Look for another software testing book.
Rating: 
Summary: An obtuse testing reference
Review: We've been developing a testing group and I wanted a practical reference for software testing. This is not it. The text presumes you're in an extremely mature environment (CMM 3 or higher) and have requirements, design, adequate resources, etc., etc.. I think the book needs more examples, better organization, and practical solutions to the difficulties you're likely to face in managing large-scale testing organizations to be truly effective. If you want LOTS of arcane procedures, though, and are going to work for a gov't. agency--this is your book!
Rating:
Summary: Every software tester should read this book!
Review: William Perry hits on many aspects of software testing and how it is impacted by other phases within the software development life cycle. This is one book that anyone involved in the testing arena needs to read. The success of test group cannnot continue without Perry's ideas.
<< 1 >>
| 
