ISBN:0201325640Book Description
While developers and IT organizations increasingly acknowledge the importance of software testing, few know how to proceed -- especially when it comes to testing advanced object-oriented software systems. In this book, two leading O-O test researchers and consultants outline a start-to-finish methodology for testing: what to test, why to test it, how to test it, who should do the testing, and when. The book is organized around a task orientation, encompassing testing models; testing components, systems and subsystems; and planning for testing. The authors review the unique challenges associated with object-oriented software testing, offer practical insights into testing priorities, introduce each leading testing technique, and walk step-by-step through applying them. They review the development of custom test software, and demonstrate how to strengthen the ties between testing and the rest of the development process. Features include a detailed object-oriented testing FAQ, and a running case study that ties together all stages and elements of O-O testing. For every IT manager, project manager, software developer and engineer, and for any professional concerned with the measurement of software quality.
/p>Reviews From AMAZON.COM
Not very practical at all
As you might expect from a couple of academic professors this book is full of formal processes that are easy to teach and write exams around but don't scale to the real world.
The book spends 47 pages covering the basics of object oriented design (class, object, inheritance etc) and UML diagrams (class diagrams, state diagrams, sequence diagrams) yet completely ignores basic testing concepts such as white and black box testing. The book also has zero coverage of popular testing tools such as JUnit and NUnit that are making a real difference in test productivity and code quality these days.
I found only two useful ideas in the book, guided inspection and orthogonal array testing. Guided inspection is documented in mind numbing detail but unfortunately the book does such a poor job of explaining orthogonal array testing that I had to go and research it on the web.
Surprisingly for a book that claims to be a practical guide the exercises are largely ambiguous and open-ended essay style questions. The authors provide snippets of a breakout-style game that they use as a running example throughout the book. The exercises could have been so much better if they had included a design and implementation of a simpler application and set practical problems based on that code. If, like me, you learn through doing then you won't get much help from this book.
I doubt I will pick this book up again anytime soon and neither will I be recommending it to any of my friends or coworkers.
the usual not practical book
The book describes object orientation. Oh, come on, folks, there are tons of books on that topic and they do it better.
The contents are very object orientation centered. In my experience as a tester, I don't care about the use language, paradigm or what ever (except for reviews of course). To me it seems that OO was new to the authors and they thought it would demand many new testing strategies, which it doesn't (after the JUnit testing of course).
The proposed procedures look very much like something used at a university, but are not practical in the real world.
I am a tester and test manager and I certainly did not found any help in here.