Module test case generation

ABSTRACT

While considerable attention has been given to techniques for developing complex systems as collections of reliable and reusable modules, little is known about testing these modules. In the literature, the special problems of module testing have been largely ignored and few tools or techniques are available to the practicing tester. Without effective testing methods, the development and maintenance of reliable and reusable modules is difficult indeed. We describe an approach for systematic module regression testing. Test cases are defined formally using a language based on module traces, and a software tool is used to automatically generate test programs that apply the cases. Techniques for test case generation in C and in Prolog are presented and illustrated in detail.

REFERENCES

• 1: Frederick P. Brooks, Jr., The mythical man-month (anniversary ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 2: IEEE Standard for Software Unit Testing. Soft. Eng. Tech. Comm. of the IEEE Computer Society, May 1987.
• 3: D L Parnas , P C Clements, A rational design process: How and why to fake it, IEEE Transactions on Software Engineering, v.12 n.2, p.251-257, Feb. 1986
• 4: D. Hoffman, Practical interface specification, Software—Practice & Experience, v.19 n.2, p.127-148, February 1989 [doi>10.1002/spe.4380190204]
• 5: Wolfram Bartussek , David Lorge Parnas, Using assertions about traces to write abstract specifications for software modules, Proceedings of the 2nd Conference of the European Cooperation on Informatics: Information Systems Methodology, p.211-236, October 10-12, 1978
• 6: D. Hoffman , Richard Thomas Snodgrass, Trace Specifications: Methodology and Models, IEEE Transactions on Software Engineering, v.14 n.9, p.1243-1252, September 1988 [doi>10.1109/32.6168]
• 7: D.M. Hoffman. A CASE study in module testing. In Proc. Conf. Software Maintenance (accepted for publication), IEEE Computer Society, October 1989.
• 8: W.E. Howden. Functional program testing. IEEE Trans. Soft. Eng., SE6(2):162-169, March 1980.
• 9: Barbara Liskov , John Guttag, Abstraction and specification in program development, MIT Press, Cambridge, MA, 1986
• 10: J.W. Duran and S.C. Ntafos. An evaluation of random testing. IEEE Trans. Soft. Eng., SE-10(4):438- 444, July 1984.
• 11: J. C. Huang, An Approach to Program Testing, ACM Computing Surveys (CSUR), v.7 n.3, p.113-128, Sept. 1975 [doi>10.1145/356651.356652]
• 12: W.E. Howden. Reliability of the path analysis testing strategy. IEEE Trans. Soft. Eng., SE-2(3):208-215, September 1976.
• 13: Timothy A. Budd , Richard A. DeMillo , Richard J. Lipton , Frederick G. Sayward, Theoretical and empirical studies on using program mutation to test the functional correctness of programs, Proceedings of the 7th ACM SIGPLAN-SIGACT symposium on Principles of programming languages, p.220-233, January 28-30, 1980, Las Vegas, Nevada [doi>10.1145/567446.567468]
• 14: 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]
• 15: D.J. Panzl. A language for specifying software tests. In Proc. AFIPS Natl. Comp. Conf., pages 609-619, AFIPS, 1978.
• 16: N. Choquet. Test data generation using a prolog with constraints. In Workshop on Software Testing, pages 132-141, IEEE Computer Society, 1986.
• 17: S. Gerhart. A Test Data Generation Method Using Prolog. Technical Report TR85-02, Wang Inst. of Grad. Studies, 1985.
• 18: Michael M. Gorlick , Carl F. Kesselman , Daniel A. Marotta , D. Scott Parker, Mockingbird: a logical methodology for testing, Journal of Logic Programming, v.8 n.1-2, p.95-119, Jan./Mar. 1990 [doi>10.1016/0743-1066(90)90053-8]
• 19: C. Wild. The Use of Generic Constraint Logic Programming for Software Testing and Analysis. Technical Report 88-02, Dept. of Computer Science, Old Dominion University, Norfolk, VA, 1988.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.m Miscellaneous
          Subjects: Reusable software**

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques
          Subjects: Modules and interfaces
      D.2.5 Testing and Debugging
          Subjects: Testing tools (e.g., data generators, coverage testing)

General Terms:
Languages, Reliability