Abstract
The usual ways of checking computer programs have important flaws. A better way to check a program you have written is to have someone else write a program that does the same thing and then compare the output of the two programs over a wide range of input. Two examples are described.
Article PDF
Similar content being viewed by others
Avoid common mistakes on your manuscript.
References
Dyckman, H. L., &Church, R. M. The TIICIE system for interactive control of independent experiments. InComputers in the psychology laboratory (Vol. 2). Maynard, Mass: Digital Equipment Corporation, 1972.
Gerhart, S., &Yelowitz, L. Observations of fallability in applications of modern programming methodology.IEEE Transactions on Software Engineering, 1976,2, 195–207.
Knuth, D. E.The art of computer programming (Vol. 2). Reading, Mass: Addison-Wesley, 1969.
McNeil, D. R., &Tukey, J. W. Higher-order diagnosis of two-way tables, illustrated on two sets of demographic empirical distributions.Biometrics, 1975, 31, 487–510.
Myers, G. L.Software reliability: Principles and practices. New York: Wiley, 1976.
Myers, G. L.The art of software testing. New York: Wiley, 1979.
Roberts, S., &Church, R. M. Control of an internal clock.Journal of Experimental Psychology: Animal Behavior Processes, 1978,4, 318–337.
Yeh, R. T. (Ed.).Current trends in programming methodology (Vol. 2). Englewood Cliffs, N.J: Prentice-Hall, 1977.
Author information
Authors and Affiliations
Additional information
I thank Russell Church for his help. This work was supported by NSF Grant BNS79-08839-01.
Rights and permissions
About this article
Cite this article
Roberts, S. How to check a computer program. Behavior Research Methods & Instrumentation 12, 155–156 (1980). https://doi.org/10.3758/BF03201592
Issue Date:
DOI: https://doi.org/10.3758/BF03201592