ACM Home Page
Please provide us with feedback. Feedback
Introduction to special section on software testing
Full text PdfPdf (697 KB)
Source
Communications of the ACM archive
Volume 31 ,  Issue 6  (June 1988) table of contents
Pages: 662 - 667  
Year of Publication: 1988
ISSN:0001-0782
Author
R. Hamlet  Department of Computer Science and Engineering, Oregon Graduate Center, Beaverton, OR
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 17,   Downloads (12 Months): 130,   Citation Count: 7
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/62959.62962
What is a DOI?

ABSTRACT

The field of software testing spans mathematical theory, the art and practice of validation, and methodology of software development. To cover this range would require a textbook (or several texts), not a trio of articles. But the work presented in this special section is a kind of "test set." Each paper is a significant contribution within one of the three broad areas. The reader must now make the assessment that is critical to any review of test points: are they representative? My own answer is 'no'; these articles are provocative and revealing rather than routine summaries. And perhaps that is what software testing is all about: good tests are the ones that provide new insights, not the ones that cover well worn ground.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Clarke, L. A system to generate test data and symbolically execute programs. IEEE Trans. Sofiw. Eng. SE-2, 5 (Sept. 1977), 215-222.
 
3
Darringer, J. and King, J. Applications of symbolic execution to program testing. Computer lI, 4 (Apr. 1978), 51-60.
 
4
DeMillo, R., Lipton, R., and Sayward, F. Hints on test data selection: Help for the practicing programmer. Computer 11, 4 (Apr. 1978), 34-43.
 
5
Duran, J. and Ntafos, S. An evaluation of random testing. IEEE Trans. Softw. Eng. SE-IO, 4 (July 1984), 438-444.
 
6
7
 
8
Hamlet, R. Other people's monitors. ACM SIGPLAN Not. 8, 7 (July 1973), 21-22.
 
9
Hamlet, R. Testing programs with the aid of a compiler. IEEE Trans. Softw. Eng. SE-3, 4 (July 1977}, 279-290.
 
10
 
11
Howden, W. Methodology for the generation of program test data. IEEE Trans. Computers C-24, 5 (May 1975}, 554-559.
 
12
Howden, W. Reliability of the path analysis testing strategy. IEEE Trans. Softw. Eng. SE-2, 5 (Sept. 1976), 208-215.
 
13
Howden, W. Weak mutation testing and completeness of test sets. IEEE Trans. Softw. Eng. SE-8, 4 (July 1982), 371-379.
14
 
15
Lonergan, L., and King, P. Design of the B5000 system. Datamation 7, (May 1961), 28-32.
 
16
Morell, L. A model for assessing code-based testing techniques. In Proceedings of the 5th Annual Pacific Northwest Software Quality Conference (Portland), 1987, 309-325.
 
17
Ramamoorthy, C., Ho, S., and Chen, W. On the automated generation of program test data. IEEE Trans. Softw. Eng. SE-2, 6 {Dec. 1976), 293-300.
 
18
 
19
Ross, S. Software reliability: The stopping rule problem. IEEE Trans. Softw. Eng. SE- 11, 12 (Dec. 1985}, 1472-~ 476.
 
20
 
21
Weiser, M., Gannon, J., and McMullin, P. Comparison of structural test coverage metrics. IEEE Softw. 2, 2 (Mar. 1985}, 80-85.
 
22
 
23
Weyuker, E. The applicability of program schema results to programs. Int. }. Computer Inform. Sci. 8, 387-.403.
 
24
Zelkowitz, M., et al. Software engineering practices in the U.S. and Japan. Computer 17, 6 tJune 1984), 57-66.