By Topic

Test data selection criteria for (software) integration testing

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Linnenkugel, U. ; Gesselschaft fur Math. und Datenverarbeitung, Bonn, West Germany ; Mullerburg, M.

When large programs are tested, a distinction is made between module testing and integration testing. During module testing, one concentrates on testing algorithms and their data, whereas during integration testing, one concentrates on testing the relations and the interfaces between the modules. The authors use the well-known criteria for module testing to define similar criteria, based on control and data flow, for the purposes of integration testing. An advantage is that it is possible to use strong test data selection criteria, such as all-loop-iteration-free-paths, when testing a single module because, generally, a module will be small. For integration testing, data flow criteria are especially useful since the aim of integration testing is to show the correctness of the interfaces between the modules which, in the case of procedures, are determined by the data flow between the calling and the called procedure

Published in:

Systems Integration, 1990. Systems Integration '90., Proceedings of the First International Conference on

Date of Conference:

23-26 Apr 1990