Glenford J. Myers
Abstract
This paper describes an experiment in program testing, employing 59 highly experienced data processing professionals using seven methods to test a small PL/I program. The results show that the popular code walkthrough/inspection method was as effective as other computer-based methods in finding errors and that the most effective methods (in terms of errors found and cost) employed pairs of subjects who tested the program independently and then pooled their findings. The study also shows that there is a tremendous amount of variability among subjects and that the ability to detect certain types of errors varies from method to method.
- 1 Fagan, M.E. Design and code inspections to reduce errors in program development. IBM Syst. J. 15, 3 (1976), 182-211.Google Scholar
Digital Library
- 2 Goodenough, J.B., and Gerhart, S.L. Toward a theory of test data selection. 1EEE Trans. Software Eng. SE-1, 2 (1975), 156-173.Google ScholarDigital Library
- 3 Gould, J.D. Some psychological evidence on how people debug computer programs. Int. J. Man-Machine Studies 7, 2 (1975), 151-182.Google ScholarCross Ref
- 4 Gould, J.D., and Drongowski, P. An exploratory study of computer program debugging. Human Factors 16, 3 (1974), 258-277.Google ScholarCross Ref
- 5 Griffith, P.F., and Henry, R.M. An investigatory study into human problem solving capabilities as they relate to programmer efficiency. Comptr. Personnel 3, 3 (1972), 10--15. Google ScholarDigital Library
- 6 Hetzel, W.C. An experimental analysis of program verification methods. Ph.D. Th., U. of North Carolina, Chapel Hill, 1976. Google ScholarDigital Library
- 7 Howden, W.E. Symbolic testing and the DISSECT symbolic evaluation system. IEEE Trans. Software Eng. SE-3, 4 (1977), 266-278.Google ScholarDigital Library
- 8 Jelinski, Z., and Moranda, P.B. Applications of a probabilitybased model to a code reading experiment. Rec. 1973 IEEE Symp. Comptr. Software Reliability, IEEE, New York, 1973, pp. 78-81.Google Scholar
- 9 Myers, G.J. Software Reliability: Principles and Practices. Wiley- Interscience, New York, 1976. Google ScholarDigital Library
- 10 Naur, P. Programming by action clusters. BIT 9, 3 (1969), 250-258.Google ScholarCross Ref
- 11 Shneiderman, B. Experimental testing in programming languages, stylistic considerations and design techniques. Proc. AFIPS 1975 NCC, AFIPS Press, Montvale, N.J., 1975, pp. 653--656.Google ScholarDigital Library
Index Terms
- A controlled experiment in program testing and code walkthroughs/inspections
Recommendations
Testing the Value of Checklists in Code Inspections
Checklists are an important part of code and design inspections. Ideally, they aim to increase the number of faults found per inspection hour by highlighting known areas of previous failure. In practice, although some researchers have quantified ...
Using code instrumentation to enhance testing on J2ME: a lesson learned with JInjector
HotMobile '09: Proceedings of the 10th workshop on Mobile Computing Systems and ApplicationsA wide range of J2ME applications are GUI-driven with significant code dedicated to handle the graphical user interface (GUI). To maximize the chances of detecting bugs, effective testing of such applications require end-to-end testing on devices; as ...
Test input reduction for result inspection to facilitate fault localization
Testing-based fault-localization (TBFL) approaches often require the availability of high-statement-coverage test suites that sufficiently exercise the areas around the faults. However, in practice, fault localization often starts with a test suite ...
Comments