A Comparison of Some Structural Testing Strategies
June 1988 (vol. 14 no. 6)
pp. 868-874
DOI Bookmark:
http://doi.ieeecomputersociety.org/10.1109/32.6165
Several structural testing strategies are compared in terms of their relative coverage of the program's structure and also in terms of the number of test cases needed to satisfy each strategy. Some of the deficiencies of such comparisons are discussed [1] T. A. Budd, "The portable mutation testing suite," Univ. Arizona, Tech. Rep. TR83-8, Mar. 1983.[2] L. A. Clarke, A. Podgurski, D. J. Richardson, and S. J. Zeil, "A comparison of data flow path selection criteria," inProc. 8th Inf. Conf. Sofware Eng.(London UK), Aug. 1985. Los Alamitos, CA: IEEE Computer Soc., 1985, pp. 244-251.[3] M. Hennel, D. Hedley, and I. J. Riddell, "Assessing a class of software tools, " inProc. 7th Int. Conf. Software Engineering, Mar. 1984, pp. 166-277.[4] P. M. Herman, "A data flow analysis approach to program testing."Australian Comput. J., vol. 8. no. 3, pp. 92-96, Nov. 1976.[5] W. E. Howden, "Methodology for the generation of program test data,"IEEE Trans. Comput., vol. C-24, no. 5, pp. 554-559, May 1975.[6] W. E. Howden, "Symbolic testing-design techniques. costs and effectiveness," NTIS PB-268518, May 1977.[7] J. C. Huang, "An approach to program testing,"ACM Comput. Surveys, vol. 7, no. 3, pp. 113-128, Sept. 1975.[8] J. Laski and B. Korel, "A data flow oriented program testing strategy,"IEEE Trans. Software Eng., vol. SE-9, no. 3, pp. 347-354, May 1983.[9] J. Laski, "On data flow guided program testing,"SIGPLAN Notices, vol. 17, pp. 62-71, Sept. 1982.[10] S. Ntafos, "On testing with required elements," inProc. COMPSAC-81, Nov. 1981, pp. 142-149.[11] S. C. Ntafos, "An evaluation of required element testing strategies,"Proc. 7th Int. Conf. Software Eng., Mar. 1984, pp. 250-256.[12] S. Ntafos, "On required element testing,"IEEE Trans. Software Eng., vol. 10, no. 6, pp. 795-803, Nov. 1984.[13] S. Ntafos, "A comparison of some structural testing strategies," inProc. 19th Hawaii Int. Conf. System Sciences, Jan. 1986, pp. 803-811.[14] S. Rapps and E. J. Weyuker, "Selecting software test data using data flow information,"IEEE Trans. Software Eng., vol. SE-11, no. 4, pp. 367-375, Apr. 1985.[15] M. D. Weiser, J. D. Gannon, and P. R. McMullin, "Comparison of structured test coverage metrics,"IEEE Software, vol. 2, no. 2, pp. 80-85, Mar. 1985.[16] E. J. Weyuker, "The complexity of data flow criteria for test data selection,"Inform. Processing Lett., vol. 19, no. 2, pp. 103-109, Aug. 1984.[17] M. R. Woodward, D. Hedley, and M. A. Hennell, "Experience with path analysis and testing of programs,"IEEE Trans. Software Eng., vol. SE-6, pp. 278-286, May 1980.
Index Terms:
program testing; structural testing; program testing; programming theory; structured programming
Citation:
S.C. Ntafos, "A Comparison of Some Structural Testing Strategies," IEEE Transactions on Software Engineering, vol. 14, no. 6, pp. 868-874, June 1988, doi:10.1109/32.6165
Usage of this product signifies your acceptance of the
Terms of Use.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb