The Community for Technology Leaders
Green Image
<p>The extension of dataflow testing to interprocedural testing is described. This was done by developing both an analysis technique that computes the required interprocedural definition-use information, for both direct and indirect dependencies and a testing technique that uses this information in selecting and executing the subpaths across procedure boundaries. A testing tool that implements this technique is presented. For the interprocedural dataflow analysis, the technique summarizes the individual procedures' definition and use information at call sites and then propagates this information throughout the interacting procedures. By efficiently computing the interprocedural data dependencies before testing, the approach lets the testing tool use existing path-selection techniques based on dataflow for interprocedural testing. To track the execution path, the technique recognizes the calls to and returns from procedures and handles the association of various names with a definition as the execution path is being inspected. The technique handles recursive procedures and supports separate compilation of procedures.</p>
integration testing; dataflow testing; interprocedural testing; analysis technique; interprocedural definition-use information; indirect dependencies; testing technique; subpaths; procedure boundaries; testing tool; interprocedural dataflow analysis; use information; call sites; interacting procedures; interprocedural data dependencies; existing path-selection techniques; execution path; recursive procedures; separate compilation; graph theory; parallel programming; program testing

M. J. Harrold and M. L. Soffa, "Selecting and Using Data for Integration Testing," in IEEE Software, vol. 8, no. , pp. 58-65, 1991.
89 ms
(Ver 3.3 (11022016))