A case study in class testing

ABSTRACT

In contrast to the explosion of activity in object-oriented design and programming, little attention has been given to object testing. In our approach, a driver class and an oracle class are developed for each class-under-test (CUT). The driver class is based on a testgraph which partially models the CUT as a state machine, but with vastly fewer states and transitions. The oracle class provides essentially the same operations as the CUT, but supports only the testgraph states and transitions. Surprisingly thorough testing is achievable with simple test graphs and oracles. The key is designing the two together, to avoid tests for which input generation and output checking are unaffordable. We illustrate our approach with a test suite developed for a class from a commercial library.

REFERENCES

• 1: Boris Beizer, Software testing techniques (2nd ed.), Van Nostrand Reinhold Co., New York, NY, 1990
• 2: {Cho78} T. S. Chow. Testing software design modeled by finite-state machines. IEEE Trans. Soft. Eng., SE-4(3): 178--187, May 1978.
• 3: Alan,M. Davis, A comparison of techniques for the specification of external system behavior, Communications of the ACM, v.31 n.9, p.1098-1115, Sept. 1988 [doi>10.1145/48529.48534]
• 4: {Fie89} S. P. Fiedler. Object-oriented unit testing. Hewlett-Packard Journal, pages 69--74, April 1989.
• 5: {Fra90} P. G. Frankl. Tools for testing object-oriented programs. In Proc. Pacific Northwest Software Quality Conf., pages 309--324, 1990.
• 6: John Gannon , Paul McMullin , Richard Hamlet, Data Abstraction, Implementation, Specification, and Testing, ACM Transactions on Programming Languages and Systems (TOPLAS), v.3 n.3, p.211-223, July 1981 [doi>10.1145/357139.357140]
• 7: Mary Jean Harrold , John D. McGregor , Kevin J. Fitzpatrick, Incremental testing of object-oriented class structures, Proceedings of the 14th international conference on Software engineering, p.68-80, May 11-15, 1992, Melbourne, Australia [doi>10.1145/143062.143093]
• 8: {Hof89} D. M. Hoffman. A CASE study in module testing. In Proc. Conf. Software Maintenance, pages 100--105. IEEE Computer Society, October 1989.
• 9: {How76} W. E. Howden. Reliability of the path analysis testing strategy. IEEE Trans. Soft. Eng., SE-2(3): 208--215, September 1976.
• 10: Daniel M. Hoffman , Paul Strooper, Automated Module Testing in Prolog, IEEE Transactions on Software Engineering, v.17 n.9, p.934-943, September 1991 [doi>10.1109/32.92913]
• 11: {HS93} D. M. Hoffman and P. A. Strooper. Graph-based class testing. In 7th Australian Software Engineering Conf. (to appear), 1993.
• 12: {iee82} Soft. Eng. Tech. Comm. of the IEEE Computer Society. IEEE Standard Glossary of Software Engineering Terminology, September 1982.
• 13: {McI69} D. McIllroy69. Mass-produced software components. In Proc. Conf. NATO Science Committee, 1969.
• 14: {MW92} G. Murphy and P. Wong. Object-oriented systems testing methodology: An overview. Technical Report TR92-0656, MPR Teltech Ltd., October 1992.
• 15: {Pan78} D. J. Panzl. A language for specifying software tests. In Proc. AFIPS Natl. Comp. Conf., pages 609--619. AFIPS, 1978.
• 16: D. E. Perry , G. E. Kaiser, Adequate testing and object-oriented programming, Journal of Object-Oriented Programming, v.2 n.5, p.13-19, Jan./Feb. 1990
• 17: {Rat9l} Rational. The C++ Booch Components-Class Catalog, 1991.
• 18: Deepinder P. Sidhu , Ting-kau Leung, Formal Methods for Protocol Testing: A Detailed Study, IEEE Transactions on Software Engineering, v.15 n.4, p.413-426, April 1989 [doi>10.1109/32.16602]
• 19: M. D. Smith , D. J. Robson, A framework for testing object-oriented programs, Journal of Object-Oriented Programming, v.5 n.3, p.45-53, June 1992
• 20: {SRWG80} G. D. Schultz, D. B. Rose, C. H. West, and J. P. Gray. Executable description and validation of sna. IEEE Transactions on Communications, COM-28(4), April 1980.
• 21: Bjarne Stroustrup, The C++ programming language (2nd ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1991
• 22: {TR92} C. D. Turner and D. J. Robson. The testing of object-oriented programs. Technical Report TR-13/92, University of Durham, 1992.
• 23: {Won92} P. Wong. Automated class exerciser (ACE) user's guide. Technical Report TR92-0655, MPR Teltech Ltd., September 1992.