The Base for Testers

What's Integration Test?

Main Index

Integration Test Definitions -

• Def#1:Integration Test is a sequence of steps or set of procedures to verify the inter-operability of various system components.
• Def#2:Integration testing (sometimes called Integration and testing and abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.

Why integration test is necessary -

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, individual subsystems are exercised through their input interface.
Integration Test is needed because
1. We need to verify interfaces of a module are provided correctly.
A module should provide a correct interface.
No modules require contradict interfaces from a same module.
2. We need to verify a module should call other module's interfaces correctly.
The caller calls callee's interface with the correct format and parameters.

• Integration & Testing, CMU
  Case 1: Allow sufficient time for testing, and plan to test COTS products early. The time needed to conduct test and integration activities is often grossly underestimated, especially for critical products undergoing changes. ...
• Integration testing - Wikipedia, the free encyclopedia
  Integration testing (sometimes called Integration and testing and ... Integration testing takes as its input modules that have been checked out by unit ...

• Owner
  Typically, Integration Test is conducted by test engineers.

• Test Techniques
  To conduct Integration Test effectively, several rules should be kept:
  1. Test engineers should know what interfaces are supported by a module.
  2. Test engineers should know how are the interfaces are called by a module.
  3. Integration test should be conducted periodically to make sure there is no integration break.

2001-2006 kibase.com. All rights reserved.