TOPIC

INTEGRATION TESTING
Definition - What does Integration
Testing mean?

Integration testing is a software testing methodology used to
test individual software components or units of code to verify
interaction between various software components and detect
interface defects.

Components are tested as a single group or organized in an
iterative manner.

Types Of Integration Testing

Top-Down

Bottom-Up

Bi-directional (sandwich)

System intregation testing (big bang)
Top-Down Integration Testing
Top-down integration testing is an integration testing
technique used in order to simulate the behaviour of the
lower-level modules that are not yet integrated.

Stubs are the modules that act as temporary replacement for
a called module and give the same output as that of the
actual product.

The replacement for the 'called' modules is known as 'Stubs'
and is also used when the software needs to interact with an
external system.
Top Down Integration - Flow Diagram

Bottom Up Testing

Each component at lower hierarchy is tested individually and
then the components that rely upon these components are
tested.

In bottom-up testing, each subsystem is tested separately and
then the full system is tested.

All the bottom or low-level modules, procedures or functions
are integrated and then tested.
Bottom Up Integration - Flow Diagram



Bi-directional Integration (Sandwich)

Bi-directional Integration, is a kind of integration testing
process that combines top-down and bottom-up testing.


Bi-directional Integration testing is a vertical incremental
testing strategy that tests the bottom layers and top layers
and tests the integrated system in the computer software
development process.


System Integration Testing(Big Bang)


Involves integrating the modules to build a complete
software system. This is considered a high-risk
approach because it requires proper documentation
to prevent failure.

This is very similar to system testing as this basically
has a whole system before starting the testing.

Phases Of Integration Testing

Two types of phases:-

Scenario testing

Defect bash
Scenario Testing

Scenario testing helps testers to explore how the software will
work in the hands of an end user.
Scenario testing is done by creating test scenarios which
replicate the end users usage.
A test scenario can be a independent test case or a series of
test cases that follow each other.
Test scenario is just a story which explains the usage of the
software by any end user.

Defect Bash Testing


It is an ad hoc testing where people performing different role
in an organization test the product together at the same time.

This is very popular among application development
companies, where the product can be used by who perform
different roles.