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:
“What if we fail to stop the erosion of cities by automobiles?... In that case America will hardly need to ponder a mystery that has troubled men for millennia: What is the purpose of life? For us, the answer will be clear, established and for all practical purposes indisputable: The purpose of life is to produce and consume automobiles.”
—Jane Jacobs (b. 1916)
“I have always felt that the real purpose of government is to enhance the lives of people and that a leader can best do that by restraining government in most cases instead of enlarging it at every opportunity.”
—Gerald R. Ford (b. 1913)
“Rule of criticism: only attend to the shape, and the purpose will manifest itself.”
—Mason Cooley (b. 1927)