Purpose
The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items. These "design items", i.e. assemblages (or groups of units), are exercised through their interfaces using Black box testing, success and error cases being simulated via appropriate parameter and data inputs. Simulated usage of shared data areas and inter-process communication is tested and individual subsystems are exercised through their input interface. Test cases are constructed to test that all components within assemblages interact correctly, for example across procedure calls or process activations, and this is done after testing individual modules, i.e. unit testing. The overall idea is a "building block" approach, in which verified assemblages are added to a verified base which is then used to support the integration testing of further assemblages.
Some different types of integration testing are big bang, top-down, and bottom-up. Other Integration Patterns are: Collaboration Integration, Backbone Integration, Layer Integration, Client/Server Integration, Distributed Services Integration and High-frequency Integration.
Read more about this topic: Integration Testing
Famous quotes containing the word purpose:
“The chief want, in every State that I have been into, was a high and earnest purpose in its inhabitants. This alone draws out “the great resources” of Nature, and at last taxes her beyond her resources; for man naturally dies out of her.”
—Henry David Thoreau (1817–1862)
“Possibly the Creator did not make the world chiefly for the purpose of providing studies for gifted novelists; but if he had done so, we can scarcely imagine that He could have offered anything much better in the way of material ...”
—Elizabeth Stuart Phelps (1844–1911)
“Art for art’s sake, with no purpose, for any purpose perverts art. But art achieves a purpose which is not its own.”
—Benjamin Constant (1767–1834)