This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
January 1982 (vol. 8 no. 1)
pp. 34-42
R.L. Probert, Department of Computer Science, University of Ottawa
A standard technique for monitoring software testing activities is to instrument the module under test with counters or probes before testing begins; then, during testing, data generated by these probes can be used to identify portions of as yet unexercised code. In this paper the effect of the disciplined use of language features for explicitly delimiting control flow constructs is investigated with respect to the corresponding ease of software instrumentation. In particular, assuming all control constructs are explicitly delimited, for example, by END IF or equivalent statements, an easily programmed method is given for inserting a minimum number of probes for monitoring statement and branch execution counts without disrupting source code structure or paragraphing. The use of these probes, called statement probes, is contrasted with the use of standard (branch) probes for execution monitoring. It is observed that the results apply to well-delimited modules written in a wide variety of programming languages, in particular, Ada.
Index Terms:
testing, Branch execution, control structures, execution count, flowgraphs, graph theory, monitors, probe basis, program instrumentation, programming language design, software probes, spanning trees, structured programs
Citation:
R.L. Probert, "Optimal Insertion of Software Probes in Well-Delimited Programs," IEEE Transactions on Software Engineering, vol. 8, no. 1, pp. 34-42, Jan. 1982, doi:10.1109/TSE.1982.234772
Usage of this product signifies your acceptance of the Terms of Use.