Testing Object-Oriented Software

By Pei HsiaJerry GaoDavid C. Kung, et al.

Object-oriented programming increases software reusability, extensibility, interoperability, and reliability. Software testing is necessary to realize these benefits by uncovering as many programming errors as possible at a minimum cost. A major challenge to the software engineering community remains how to reduce the cost while improving the quality of software testing. The requirements for testing object-oriented programs differ from those for testing conventional programs.

Testing Object-Oriented Software illustrates these differences and discusses object-oriented software testing problems, focusing on the difficulties and challenges testers face. The text contains of nineteen reprinted papers providing a general framework for class- and system-level testing and examines object-oriented design criteria and high testability metrics. It offers object-oriented testing techniques, ideas and methods for unit testing, and object-oriented program integration-testing strategy.

Readers are shown how to drastically reduce regression test costs, presented with steps for object-oriented testing, and introduced to object-oriented test tools and systems. The book's intended audience includes object-oriented program testers, program developers, software project managers, and researchers working with object-oriented testing.

• Format: Paperback
• Language: English
• ISBN: 0818685204
• ISBN13: 9780818685200
• Release Date: November 1998
• Publisher: Wiley-IEEE Computer Society PR
• Length: 284 Pages
• Weight: 1.42 lbs.
• Dimensions: 0.6" x 8.6" x 11.0"

Customer Reviews

Excellent overview of OO testing

As far as I know, there are less than 100 articles on OO testing -- this book covers the relatively new field in seven well-organized chapters, from its problems to integration testing and test methodologies. Perhaps something more could be done with specific approaches to conducting OO testing for C++ or Java programs, but I found the book helpful in its approach to identify specific OO testing problems in the first chapter...