Integration Testing

Integration Testing is also called as 'Interface Testing'. After writing the code and finishing the unit testing (of the different - different modules), programmers focus on interconnection of those programs (modules).

Integration
Integration Testing
In order to integrate the programs/modules the programmers use one of the following methods/approaches:

  1. Top Down Approach
  2. Bottom Up Approach
  3. Hybrid Approach
  4. System Approach or Big Bang Approach
Top Down Approach:

The integration of the main module with some of the sub- modules is called as top down approach. In the place of under constructive sub modules, programmers use temporary programs which is called as 'stubs'.

Top Down Approach
Top Down Approach

Bottom Up Approach:


The Integration of sub-modules without interconnecting with main module is called as Bottom Up approach. In the place of under constructive main module programmers use a temporary program which is called as calling 'driver' or 'calling' program.

Bottom Up Approach
Bottom Up Approach


Hybrid Approach:

This approach is also called as 'Sand witch' approach. The combination of top down and bottom up approach is called as hybrid approach.

Hybrid Approach
Hybrid Approach



System Approach or Big Bang Approach:

In this approach Integration Testing starts only after the 100% completion of the coding. This the only reason that in this approach stubs or drivers are not required.


Learn Next- System Testing or Software Testing