Integration Testing
What is Integration Testing?
• NTEGRATION TESTING is defined as a type of
testing where software modules are
integrated logically and tested as a group. A
typical software project consists of multiple
software modules, coded by different
programmers. The purpose of this level of
testing is to expose defects in the interaction
between these software modules when they
are integrated.
Why do Integration Testing?
• A Module, in general, is designed by an individual
software developer whose understanding and
programming logic may differ from other
programmers. Integration Testing becomes necessary
to verify the software modules work in unity
• At the time of module development, there are wide
chances of change in requirements by the clients.
These new requirements may not be unit tested and
hence system integration Testing becomes necessary.
Example of Integration Test Case
Approaches, Strategies, Methodologies of
Integration Testing
• Big Bang Approach :
• Incremental Approach: which is further
divided into the following
– Top Down Approach
– Bottom Up Approach
– Sandwich Approach - Combination of Top Down
and Bottom Up
Big Bang Testing
• Big Bang Testing is an Integration testing
approach in which all the components or
modules are integrated together at once and
then tested as a unit. This combined set of
components is considered as an entity while
testing. If all of the components in the unit are
not completed, the integration process will
not execute.
• Advantages:
1 Convenient for small systems.
• Disadvantages:
1 Fault Localization is difficult
2 Since the Integration testing can commence
only after "all" the modules are designed,
the testing team will have less time for
execution in the testing phase.
Incremental Testing
• Bottom Up
• Top Down
• Stubs and Drivers
Stubs and Drivers
• Stub: Is called by the Module under Test.
• Driver: Calls the Module to be tested.
Bottom-up Integration Testing
• Bottom-up Integration Testing is a strategy in
which the lower level modules are tested first.
These tested modules are then further used to
facilitate the testing of higher level modules.
The process continues until all modules at top
level are tested. Once the lower level modules
are tested and integrated, then the next level
of modules are formed.
• Advantages:
• Fault localization is easier.
• No time is wasted waiting for all modules to
be developed unlike Big-bang approach
• Disadvantages:
• Critical modules (at the top level of software
architecture) which control the flow of
application are tested last and may be prone
to defects.
• An early prototype is not possible
Top-down Integration Testing
• Top Down Integration Testing is a method in
which integration testing takes place from top
to bottom following the control flow of
software system. The higher level modules are
tested first and then lower level modules are
tested and integrated in order to check the
software functionality. Stubs are used for
testing if some modules are not ready.
• Advantages:
• Fault Localization is easier.
• Possibility to obtain an early prototype.
• Critical Modules are tested on priority; major
design flaws could be found and fixed first.
• Disadvantages:
• Needs many Stubs.
• Modules at a lower level are tested
inadequately.
Sandwich Testing
• Sandwich Testing is a strategy in which top
level modules are tested with lower level
modules at the same time lower modules are
integrated with top modules and tested as a
system. It is a combination of Top-down and
Bottom-up approaches therefore it is
called Hybrid Integration Testing. It makes use
of both stubs as well as drivers.
