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:
“Along the journey we commonly forget its goal. Almost every vocation is chosen and entered upon as a means to a purpose but is ultimately continued as a final purpose in itself. Forgetting our objectives is the most frequent stupidity in which we indulge ourselves.”
—Friedrich Nietzsche (1844–1900)
“As peace is the end of war, so to be idle is the ultimate purpose of the busy.”
—Samuel Johnson (1709–1784)
“To every thing there is a season, and a time to every purpose under the heaven:
A time to be born, and a time to die; a time to plant, and a time to pluck up that which is planted;”
—Bible: Hebrew Ecclesiastes (l. III, 1–2)