Nothing Special   »   [go: up one dir, main page]

skip to main content
10.1145/75308.75320acmconferencesArticle/Chapter ViewAbstractPublication PagesisstaConference Proceedingsconference-collections
Article
Free access

Module test case generation

Published: 01 November 1989 Publication History

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]
F.P. Brooks. The Mythical Man-Month. Addison- Wesley, 1975.
[2]
IEEE Standard for Software Unit Testing. Soft. Eng. Tech. Comm. of the IEEE Computer Society, May 1987.
[3]
D.L. Parnas and P.C. Clemeuts. A rational design process: how and why to fake it. IEEE Trans. Soft. Eng., SE-12(2):251-257, February 1986.
[4]
D.M. Hoffman. Practical interface specification. Sojtware - Practice and Experience, 19(2):127-148, February 1989.
[5]
Wolfram Bartussek and David L. Parnas. Using traces to write abstract specifications for software modules. In Information Systems Methodology, pages 211-236, Springer-Verlag, 1978. Proc. 2nd Conf. European CO- operation in Informatics, October 10-12, 1978.
[6]
D.M. Hoffman and R. Snodgrass. Trace specifications: methodology and models. IEEE Trans. Soft. Eng., 14(9), 1988.
[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]
B. Liskov and J. Guttag. Abstraction and Specification in Program Development. The MIT Press, 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, 7(3):113-128, September 1975.
[12]
W.E. Howden. Reliability of the path analysis testing strategy. IEEE Trans. Soft. Eng., SE-2(3):208-215, September 1976.
[13]
T.A. Budd, R.A. DeMillo, R. J. Lipton, and F.G. Sayward. Theoretical and empirical studies on using program mutation to test the functional correctness of programs. In Proc. Principles Prog. Lang., pages 220-233, ACM, 1980.
[14]
J. Gannon, P. McMullin, and R. Hamlet. Dataabstraction implementation, specification and testing. ACM Trans. Program. Lang. Syst., 3(3):211-223, July 1981.
[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]
M.M. Gorlick, C.D. Kesselman, D.A. Marotta, and D.S. Parker. Mockingbird: a logical methodology for testing. Journal of Logic Programming (to appear), 1988.
[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.

Cited By

View all
  • (2004)Infrastructure support for controlled experimentation with software testing and regression testing techniquesProceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04.10.1109/ISESE.2004.1334894(60-70)Online publication date: 2004
  • (2000)Automatically Checking an Implementation against Its Formal SpecificationIEEE Transactions on Software Engineering10.1109/32.82576626:1(55-69)Online publication date: 1-Jan-2000
  • (1999)Testing evolving softwareJournal of Systems and Software10.1016/S0164-1212(99)00037-047:2-3(173-181)Online publication date: 1-Jul-1999
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
TAV3: Proceedings of the ACM SIGSOFT '89 third symposium on Software testing, analysis, and verification
November 1989
229 pages
ISBN:0897913426
DOI:10.1145/75308
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 November 1989

Permissions

Request permissions for this article.

Check for updates

Qualifiers

  • Article

Conference

TAV-3
Sponsor:
TAV-3: 3rd Workshop on Software Testing Verification & Analysis
December 13 - 15, 1989
Florida, Key West, USA

Upcoming Conference

ISSTA '25

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)79
  • Downloads (Last 6 weeks)11
Reflects downloads up to 25 Feb 2025

Other Metrics

Citations

Cited By

View all
  • (2004)Infrastructure support for controlled experimentation with software testing and regression testing techniquesProceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04.10.1109/ISESE.2004.1334894(60-70)Online publication date: 2004
  • (2000)Automatically Checking an Implementation against Its Formal SpecificationIEEE Transactions on Software Engineering10.1109/32.82576626:1(55-69)Online publication date: 1-Jan-2000
  • (1999)Testing evolving softwareJournal of Systems and Software10.1016/S0164-1212(99)00037-047:2-3(173-181)Online publication date: 1-Jul-1999
  • (1996)Analyzing Regression Test Selection TechniquesIEEE Transactions on Software Engineering10.1109/32.53695522:8(529-551)Online publication date: 1-Aug-1996
  • (1996)An environment to support micro-incremental class developmentAnnals of Software Engineering10.1007/BF020638112:1(213-236)Online publication date: Dec-1996
  • (1995)Integration testing based on software couplingsCOMPASS '95 Proceedings of the Tenth Annual Conference on Computer Assurance Systems Integrity, Software Safety and Process Security'10.1109/CMPASS.1995.521883(13-23)Online publication date: 1995
  • (1993)Developmental testing of abstract data typesProceedings of 1993 IEEE 17th International Computer Software and Applications Conference COMPSAC '9310.1109/CMPSAC.1993.404214(49-55)Online publication date: 1993
  • (1992)A data flow coverage testing tool for C[1992] Proceedings of the Second Symposium on Assessment of Quality Software Development Tools10.1109/AQSDT.1992.205829(2-10)Online publication date: 1992
  • (1991)Case studies on testing object-oriented programsProceedings of the symposium on Testing, analysis, and verification10.1145/120807.120822(165-177)Online publication date: 1-Oct-1991
  • (1991)Test-Case Generation from Prolog-Based SpecificationsIEEE Software10.1109/52.737498:2(49-57)Online publication date: 1-Mar-1991
  • Show More Cited By

View Options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Login options

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media