Partition Testing Does Not Inspire Confidence

IEEE Transactions on Software Engineering

Volumn 16, Issue 12, 1990, Pages 1402-1411

  Hamlet, Dick ^a   Taylor, Ross ^b  

^a PORTLAND STATE UNIVERSITY   (United States)

^b TEKTRONIX INC   (United States)

Author keywords

Partition testing; random testing; reliability; software testing theory

Indexed keywords

COMPUTER SYSTEMS, DIGITAL - RELIABILITY;

PARTITION TESTING; RANDOM TESTING;

COMPUTER SOFTWARE;

EID: 0025530786     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.62448     Document Type: Article

References (12)

1. J. Goodenough and S. Gerhart, “Toward a theory of test data selection,” IEEE Trans. Software Eng., vol. SE-1, pp. 156–173, 1975.
2. D. Richardson and L. Clarke, “A partition analysis method to increase program reliability,” in Proc. 5th Int. Conf. Software Engineering, San Diego, CA, 1981, pp. 244–253.
3. J. Duran and S. Ntafos, “An evaluation of random testing,” IEEE Trans. Software Eng., vol. SE-10, pp. 438–444, July 1984.
4. R. Glass, Modern Programming Practices. Englewood Cliffs, NJ: Prentice-Hall, 1982.
5. R. Hamlet, “Probable correctness theory,” Inform. Processing Lett., vol. 25, pp. 17–25, Apr. 1987.
6. E. Weyuker and T. Ostrand, “Theories of program testing and the application of revealing subdomains,” IEEE Trans. Software Eng., vol. SE-6, pp. 236–246, 1980.
7. L. Morell, “A model for assessing code-based testing techniques,” in Proc. 5th Annu. Pacific Northwest Software Quality Conf, Portland, OR, 1987, pp. 309–325.
8. H. Mills, V. Basili, J. Gannon, and R. Hamlet, Principles of Computer Programming: A Mathematical Approach. Boston, MA, Allyn and Bacon, 1987.
9. G. Myers, The Art of Software Testing. New York: Wiley, 1979.
10. L. G. Valiant, “A theory of the learnable,” Commun. ACM, vol. 27, pp. 1134–1142, Nov. 1984.
11. D. Angluin and P. Laird, “Identifying k-CNF formulas from noisy examples,” Yale Univ., Tech. Rep. YALEU/DCS/TR-478, June 1986.
12. R. Taylor, “An example of large-scale random testing,” in Proc. 7th Annu. Pacific Northwest Software Quality Conf, Portland, OR, 1989, pp. 339–348.