Scribd
Upload
193 views12 pages

Integration Testing Overview

Integration testing involves combining software modules into groups and testing their interaction. It occurs after unit testing individual modules and before validation testing of the full system. There are three main integration testing strategies: big bang, top-down, and bottom-up. Big bang integrates all modules at once. Top-down starts with the main module and adds subordinate modules. Bottom-up groups low-level modules into clusters and combines clusters moving up the program structure. The purpose is to test interfaces and ensure correct interactions between components.

Uploaded by

shahhoney
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
193 views12 pages

Integration Testing Overview

Integration testing involves combining software modules into groups and testing their interaction. It occurs after unit testing individual modules and before validation testing of the full system. There are three main integration testing strategies: big bang, top-down, and bottom-up. Big bang integrates all modules at once. Top-down starts with the main module and adds subordinate modules. Bottom-up groups low-level modules into clusters and combines clusters moving up the program structure. The purpose is to test interfaces and ensure correct interactions between components.

Uploaded by

shahhoney
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Introduction

Integration testing (sometimes called Integration


and Testing, abbreviated "I&T") is the phase
in software testing in which individual software
modules are combined and tested as a group.
It is a systematic technique for constructing the s/w
architecture while at the same time conducting tests to
uncover errors associated with interfacing

It occurs after unit testing and before validation
testing.
Integration testing takes as its input modules that have
been unit tested, groups them in larger aggregates.
Applies tests defined in an integration test plan to
those aggregates.
It delivers as its output the integrated system ready
for system testing.
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.

Different types of Integration Testing Strategies
Big bang
Top-Down
Bottom-Up
Big Bang
In this approach, all or most of the developed modules are
coupled together to form a complete software system or
major part of the system and then used for integration
testing.
The Big Bang method is very effective for saving time in the
integration testing process.
A type of Big Bang Integration testing is called Usage
Model testing.
Usage Model Testing can be used in both software and
hardware integration testing.
The basis behind this type of integration testing is to run
user-like workloads in integrated user-like environments.
Integration Testing
Top down integration:
Steps involved:
The main control module is used as a test driver and stubs are
substituted for all components directly subordinate to the
main control module.
Depending on the integration approach selected, subordinate
stubs are replaced one at a time with actual components.
Tests are conducted as each component is integrated.
On completion of each set of tests, another stub is replaced
with the real component.
Regression testing may be conducted to ensure that new
errors have not been introduced.
8
Top Down Integration
9
top module is tested with
stubs
stubs are replaced one at
a time, "depth first"
as new modules are integrated,
some subset of tests is re-run
A
B
C
D E
F G
Integration Testing
Bottom-up integration:
It is implemented with foll. Steps:
Low-level components are combined into clusters
that perform a specific s/w subfunction.
A driver is written to coordinate test case input and
output.
The cluster is tested.
Drivers are removed and clusters are combined
moving upward in the program structure.

10
Bottom-Up Integration
11
drivers are replaced one at a
time, "depth first"
worker modules are grouped into
builds and integrated
A
B
C
D E
F G
cluster



THE END

You might also like