Integrating testing techniques through process programming

ABSTRACT

Integration of multiple testing techniques is required to demonstrate high quality of software. Technique integration has four basic goals: reduced development costs, incremental testing capabilities, extensive error detection, and cost-effective application. We are experimenting with the use of process programming as a mechanism for integrating testing techniques. Having set out to develop a process that provides adequate coverage and comprehensive fault detection, we proposed synergistic use of DATA FLOW testing and RELAY to achieve all four goals. We developed a testing process program much as we would develop a software product from requirements through design to implementation and evaluation. We found process programming to be effective for explicitly integrating the techniques and achieving the desired synergism. Used in this way, process programming also mitigates many of the other problems that plague testing in the software development process.

REFERENCES

• CPRZ86: Lori A. Clarke, Andy Podgurski, Debra J. Richardson, and Steven J. Zeil. An investigation of data flow path selection criteria. In Proceedings of the ACM SIG- SOFT/IEEE Workshop on Software Testing, pages 23- 32, Banff, Canada, July 1986.
• CRZ88: Lori A. Clarke , Debra J. Richardson , Steven J. Zeil, TEAM: a support environment for testing, evaluation, and analysis, Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments, p.153-162, November 28-30, 1988, Boston, Massachusetts, United States
• DGK+88: R. A. DeMillo, D. S. Guindi, K. N. King, W. M. Mc- Cracken, and A. J. Offutt. An extended overview of the mothra software testing environment. In Proceedings of the ACM SIGSOFT/IEEE Second Workshop on Sojware Testing, Analysis and Verijication, Banff, Canada, July 1988. IEEE.
• DLS78: Richard DeMillo, R.J. Lipton, and F.G. Sayward. Hints on test data selection: help for the practicing programmer. Computer, 4(11), April 1978.
• LK83: Janusz W. Laski and Bogdan Korel. A data flow oriented program testing strategy. IEEE Transactions on Software Engineering, SE-9(3):347-354, May 1983.
• Nta84: Simeon C. Ntafos. On required element testing. IEEE Transactions on Software Engineering, SE-10(6):795- 803, November 1984.
• Ost87: L. Osterweil, Software processes are software too, Proceedings of the 9th international conference on Software Engineering, p.2-13, March 1987, Monterey, California, United States
• RAO89: Debra Richardson, Stephanie Leif Aha, and Leon Osterweil. A process program that integrates testing techniques. Technical Report 89-18, University of California, Irvine, 1989.
• RC85: D J Richardson , L A Clarke, Testing techniques based on symbolic evaluation, Proceedings of Centre for Software Reliability Workshop on Software: requirements, specification and testing, p.93-110, June 1986, Univ. of East Anglia, Norwich, United Kingdom
• Rea89: Reasoning Systems, Palo Alto, California. REFINE User's Guide, 1989.
• RT88: Debra J. Richardson and Margaret C. Thompson. The RELAY model of error detection and its application. In Proceedings of the ACM SIGSOFT/IEEE Second Workshop on Software Testing, Analysis and Verification, Banff, Canada, July 1988.
• RW85: Sandra Rapps , Elaine J. Weyuker, Selecting software test data using data flow information, IEEE Transactions on Software Engineering, v.11 n.4, p.367-375, April 1985 [doi>10.1109/TSE.1985.232226]
• Sut88: Stanley Sutton, Jr. The APPLA/A programming language background, interim definition, and status. Technical Report CU-88-11, Arcadia, October 1988.
• TBC+88: Richard N. Taylor , Frank C. Belz , Lori A. Clarke , Leon Osterweil , Richard W. Selby , Jack C. Wileden , Alexander L. Wolf , Michael Young, Foundations for the Arcadia environment architecture, Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments, p.1-13, November 28-30, 1988, Boston, Massachusetts, United States

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.4 Software/Program Verification
          Subjects: Correctness proofs

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Experimentation, Management, Reliability, Verification