Integration Testing

Integration Testing

Why Integration Testing?

The software market grows quickly and user demands are constantly increasing which requires the development of increasingly complex and multi-level software systems. Alongside, the system capacity requires flawless integration with third-party software.

Consisting of several integrated modules, every software requires checking of each of its units one by one as well as their combinations. In order to mitigate any malfunctions of integrated units, QATestLab provides integration testing by evaluating the behavior of the system modules as a whole.

Each unit possesses different programming logic that may affect the work of the other modules after their integration as they have been developed by various programmers. The aim of integration testing is to ensure system modules do not interfere with each other in particular combinations and satisfy all the requirements.

How We Test

In order to provide thorough integration testing, we follow several approaches. For verification of small systems, we apply the Big Bang approach by testing all integrated units at once. If only some modules are ready for testing and the duration of the test phase is limited, we implement an incremental approach by combining several modules which are logically related.

For the incremental method, we conduct “top down” or “bottom up” integration. Following the bottom up strategy, we verify the work of integrated modules starting from lower levels. Top down integration begins with testing modules from a higher level keeping the control flow of the system.

integration testing

When to start

Integration testing pic 

A traditional integration testing model suits projects following the waterfall model. Adapting to the rules of the current software market, we perform manual testing or write automated scripts for projects with continuous integration.

Integration testing is only complete if all designed tests are passed end-to-end. To avoid delays in release and the additional costs due to defect removal in high-level architecture, integration testing detects issues in the early stages.