[.ca] Testing Object-Oriented Systems: Models, Patterns, and Tools (ISBN 0201809389)

Quantity not Quality:
I am a graduate student and I'm using this book for a class. The book is very theoretical with too few examples. At first it seems that the book was written for a novice with very little computer science background since the author has the need to explain the core vocabulary in computer science. That is not the case as the later chapters get into more advanced topics, but lack the proper explanation. The book presents many test patterns but fails to include examples which would guide one in developing a test suites with the presented patterns. Some of the examples that are provided include mistakes which would misguide a novice learner. The reading is frustrating at times due to lack of appropriate explanations. As the subject of this review states, it seems the author wanted to write a really lengthy book not giving enough attention to the quality of the material presented.

A bit too much of theory..:
I bought this book after reading the previous reviews. I am a QA engineer working in OO systems, and I must say that I did not find this book to all that great. It is a good book, but I found it to be a bit theoretical. I would have welcomed more practical tips say on how to do performance testing on multitier systems, how do you adapt these concepts on hybrid systems etc.

Serious about QA read this:
I have nearly twenty years experience in IT, 12 in OO. this by far and away the most clear, useful and thought provoking work I have ever read on testing. Anyone in the OO world who is serious about testing and has not read this book is a fraud. The sad thing about this book is that those who need to read it probably will not.

Great civerage of OOP testing:
This book is an excellent source for the novice and the experienced SQA Engineer. It covers most aspects of SW testing at a very practical level. Explanations and illustrations are well focused and the code samples can save you many hours of design and implementation time.

A Must-Have:
I have several books on software testing, but none of them provides the comprehensive, in-depth coverage of testing that this book provides. No software developer or test engineer working with OO techniques should be about it!