INTEGRATION TESTING is a level of software testing where individual units / components are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing.
integration testing: Testing performed to expose defects in the interfaces and in the
interactions between integrated components or systems. See also component integration testing, system integration testing.
component integration testing: Testing performed to expose defects in the interfaces and interaction between integrated components.
system integration testing: Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange, Internet).
There are mainly two types of integration testing:
Unit / Component Integration Testing
This type of integration testing focuses on the interactions and interfaces between integrated units / components. Unit integration testing is performed after unit testing, and is generally automated. In iterative and incremental development, unit integration tests are usually part of the continuous integration process.
System Integration Testing
This type of integration testing focuses on the interactions and interfaces between systems (A system is a group of interacting or interrelated entities that form a unified whole). The other system that needs to be integrated with can either be internal or external (developed by someone else over which the organization has no control). Such systems are normally exposed via an Application Programming Interface (API) or a Microservice.
System Integration testing may be done after System Testing or in parallel with it.
There are basically four approaches to Integration Testing:
This is an approach to Integration Testing where all or most of the units are combined together and tested at one go. This approach is taken when the testing team receives the entire software in a bundle. So what is the difference between Big Bang Integration Testing and System Testing? Well, the former tests only the interactions between the units while the latter tests the functionalities in the entire system.
This is an approach to Integration Testing where top-level units are tested first and lower level units are tested step by step after that. This approach is taken when a top-down development approach is followed. Test Stubs are needed to simulate lower level units which may not be available during the initial phases.
This is an approach to Integration Testing where bottom level units are tested first and upper-level units step by step after that. This approach is taken when a bottom-up development approach is followed. Test Drivers are needed to simulate higher level units which may not be available during the initial phases.
This is an approach to Integration Testing which is a combination of Top Down and Bottom Up approaches.
Tips for Selenium Testing
Ensure that you have a proper Architecture / Technical Design document where interactions between each unit are clearly defined. In fact, you will not be able to perform Integration Testing without this information.
Ensure that you have a robust Software Configuration Management system in place. Or else, you will have a tough time tracking the right version of each unit, especially if the number of units to be integrated is many.
Make sure that each unit is unit tested before you start Integration Testing.
As far as possible, automate your tests, especially when you use the Top Down or Bottom-Up approach, because regression testing is important each time you integrate a unit and manual regression testing can be tedious/inefficient.