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:
“I beg to assure you that I have never written you, or spoken to you, in greater kindness or feeling than now, nor with a fuller purpose to sustain you, so far as in my most anxious judgement, I consistently can. But you must act.”
—Abraham Lincoln (1809–1865)
“Happiness serves hardly any other purpose than to make unhappiness possible.”
—Marcel Proust (1871–1922)
“And the purpose of the many stops and starts will be made clear:
Backing into the old affair of not wanting to grow
Into the night, which becomes a house, a parting of the ways
Taking us far into sleep. A dumb love.”
—John Ashbery (b. 1927)