A Functional Approach to Program Testing and Analysis

IEEE Transactions on Software Engineering

Volumn SE-12, Issue 10, 1986, Pages 997-1005

  Howden, William E ^a  

^a UNIVERSITY OF CALIFORNIA   (United States)

Author keywords

Analysis; dynamic analysis; functions; input output; interfaces; operators; sequence analysis; static analysis; testing; theory validation

Indexed keywords

COMPUTER INTERFACES; COMPUTER PROGRAMMING - ANALYSIS;

FUNCTIONAL APPROACH;

COMPUTER SOFTWARE;

EID: 0022789899     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1986.6313016     Document Type: Article

References (42)

1. C. V. Ramamoorthy and S. F. Ho, “Testing large software with automated software evaluation systems,” IEEE Trans. Software Eng., vol. SE-1, 1975.
2. L. Osterweil and L. Fosdick, “DAVE—A validation error detection and documentation system for FORTRAN programs,” Software Practice and Experience, vol. 6, pp. 473–486, 1976.
3. R. N. Taylor, “A general purpose a algorithm for analyzing concurrent programs,” Commun. ACM, vol. 26, no. 3, pp. 362–376, 1983.
4. W. E. Howden, “Symbolic testing and the DISSECT symbolic evaluation system,” IEEE Trans. Software Eng., vol. SE-3, pp. 266–278, 1977.
5. L. A. Clarke, “A system to generate test data and symbolically execute programs,” IEEE Trans. Software Eng., vol. SE-2, pp. 215–222, 222, 1976.
6. J. C. King, “Symbolic execution and program testing,” Commun. ACM, vol. 19, no. 7, pp. 385–394, 1976.
7. T. E. Cheatham, G. H. Holloway, and T. A. Townley, “Symbolic evaluation and the analysis of programs,” IEEE Trans. Software Eng., vol. SE-5, pp. 402–417, 1979.
8. R. S. Boyer, B. Elpas, and K. N. Levitt, “SELECT—A formal system for testing and debugging programs by symbolic execution,” in Proc. Int. Conf. Reliable Software, IEEE, 1975, pp. 234–245.
9. J. A. Darringer and J. C. King, “Applications of symbolic execution to program testing,” Computer, vol. 11, pp. 51–60, 1978.
10. J. C. Huang, “Program instrumentation and software testing,” Computer, vol. 11, pp. 25–33, 1978.
11. J. Goodenough and S. C. Gerhart, “Toward a theory of test data selection,” IEEE Trans. Software Eng., vol. SE-1, no. 2, pp. 156–173, 1975.
12. E. J. Weyuker and T. J. Ostrand, “Theories of program testing and the application of revealing subdomains,” IEEE Trans. Software Eng., pp. 236–246, 1980.
13. E. J. Weyuker, “Assessing test data adequacy through program inference,” ACM Trans. Program. Lang. Syst., vol. 5, no. 4, pp. 641–655, 655, 1983.
14. R. G. Hamlet, “Reliability theory of program testing,” Acta Inform., vol. 16, pp. 31–43, 1981.
15. T. A. Budd and D. Angluin, “Two notions of correctness and their relation to testing,” Acta Inform., vol. 18, pp. 31–45, 1982.
16. W. E. Howden, “Reliability of the path analysis testing strategy,” IEEE Trans. Software Eng., vol. SE-2, 1976.
17. —, “Theoretical and empirical studies of program testing,” IEEE Trans. Software Eng., vol. SE-4, no. 4, 1978.
18. —, “Proving correctness by testing,” APIS, Univ. California, Davis, Tech. Rep., 1974.
19. —, “Algebraic program testing,” Acta Inform., vol. 10, no. 1, 1978.
20. W. E. Howden and P. Eichhorst, “Proving properties of programs from program traces,” in Software Testing and Validation Techniques, E. Miller and W. E. Howden, Eds. Long Beach, CA: IEEE, 1978.
21. M. Brooks, “Determining correctness by testing,” Stanford Univ., Tech. Rep. 80–804, 1980.
22. 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. Symp. Principles of Programming Languages, ACM, 1980.
23. M. Geller, “Test data as an aid in proving program correctness,” in Proc. Symp. Principles of Programming Languages, ACM, 1976.
24. W. E. Howden, “Weak mutation testing and completeness of program test sets,” IEEE Trans. Software Eng., vol. SE-8, no. 4, pp. 371–379, 1981.
25. K. A. Foster, “Error sensitive test case analysis,” IEEE Trans. Software Eng., vol. SE-6, 1978.
26. —, “Sensitive test data for logic expressions,” ACM Software Eng. Notes, vol. 9, no. 2, 1984.
27. J. W. Duran and S. Ntafos, “A report on random testing,” Univ. Texas of Dallas, Comp. Sci. Rep. 83.
28. R. A. Thayer, M. Lipov, and E. C. Nelson, Software Reliability. Amsterdam, The Netherlands: North-Holland, 1978.
29. W. E. Howden, “Functional program testing,” IEEE Trans. Software Eng., vol. SE-6, no. 3, 1980.
30. —, Functional Program Testing and Analysis. New York: McGraw-Hill, in press.
31. T. DeMarco, Structural Analysis and System Specification. New York: Yourdon, 1978.
32. E. Yourdon and L. Constantine, Structured Design. Englewood Cliffs, NJ: Prentice-Hall, 1979.
33. S. H. Caine and E. K. Gordon, “PDL—A tool for software design,” in Proc. Nat. Comput. Conf., 1975.
34. L. G. Stucki, “Automatic generation of self metric software,” in Proc. IEEE Symp. Comput. Software Rel., 1973, pp. 94–100.
35. W. E. Howden, “Methodology for the generation of program test data,” IEEE Trans. Comput., vol. C-24, 1975.
36. P. M. Herman, “A data flow analysis approach to program testing,” Australian Comput. J., vol. 8, no. 3, 1976.
37. J. W. Laski and B. Korel, “A data flow oriented program testing strategy,” IEEE Trans. Software Eng., vol. SE-9, no. 3, 1983.
38. S. C. Ntafos, “An evaluation of required element testing strategies,” IEEE Trans. Software Eng., vol. SE-10, no. 6, 1984.
39. S. Rapps and E. J. Weyuker, “Selecting software test data using data flow information,” IEEE Trans. Software Eng., vol. SE-11, no. 4, 1985.
40. L. J. White and E. I. Cohen, “A domain strategy for program testing,” IEEE Trans. Software Eng., vol. SE-6, no. 3, 1980.
41. D. J. Panzl, “Automatic software test drivers,” Computer, vol. 11, no. 4, pp. 44–50, 1978.
42. S. J. Zeil, “Testing for pertubations of program statements,” IEEE Trans. Software Eng., vol. SE-9, no. 3, pp. 335–346, 1983.