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 Omnibus
Had no real purpose till it got to us.
Never believe it.”
—Robert Frost (1874–1963)
“The purpose of a work of fiction is to appeal to the lingering after-effects in the reader’s mind as differing from, say, the purpose of oratory or philosophy which respectively leave people in a fighting or thoughtful mood.”
—F. Scott Fitzgerald (1896–1940)
“The purpose of education is to keep a culture from being drowned in senseless repetitions, each of which claims to offer a new insight.”
—Harold Rosenberg (1906–1978)