Integration Testing is a degree of programming testing where singular units are consolidated and tried as a gathering. The motivation behind this degree of testing is to uncover blames in the association between coordinated units. Test pilots and test stubs are utilized in System Integration Testing.
Definition by ISTQB
Integration testing: Testing performed to uncover surrenders in the interfaces and in the
cooperation between incorporated parts or frameworks.
Component integration testing: Testing performed to uncover surrenders in the interfaces and
association between coordinated parts.
System integration testing: Testing the reconciliation of frameworks and bundles; testing
interfaces to outer associations.
Objectives of integration testing
Big Bang is a way to deal with Integration Testing where all or the greater part of the units are consolidated together and tried at one go. This methodology is taken when the testing group gets the whole programming in a pack. So what is the contrast between Big Bang Integration Testing and System Testing? Indeed, the previous tests just the connections between the units while the last tests the whole framework.
Top-Down is a way to deal with Integration Testing where top-level units are tried first and lower-level units are tried bit by bit after that. This methodology is adopted when top-down improvement strategy is pursued. Test Stubs are expected to mimic lower-level units which may not be accessible during the underlying stages.
Bottom-Up is a way to deal with Integration Testing where base level units are tried first and upper-level units bit by bit after that. This methodology is adopted when the base up improvement strategy is pursued. Test pilots are expected to reproduce more significant level units which may not be accessible during the underlying stages.
Sandwich/Hybrid is a way to deal with Integration Testing which is a blend of Top-Down and Bottom-Up Approaches.
Guarantee that you have a legitimate Detail Design record where cooperations between every unit are plainly characterized. Truth be told, you won’t have the option to perform Integration Testing without this data.
Ensure that you have a strong Software Configuration Management framework set up. Or the consequences will be severe, you will make some intense memories following the correct rendition of every unit, particularly if the quantity of units to be incorporated is gigantic.
Ensure that every unit will be unit tried before you start Integration Testing.
Beyond what many would consider possible, automate your tests, particularly when you utilize the Top-Down or Bottom-Up approach, since regression testing is significant each time you incorporate a unit, and manual regression testing can be wasteful.