Integration Testing!
It is been conceptualized for testing of the interfaces and integration between peripheral, forming a synergy among the different components of the operating system, hardware and file system interfaces between the system.
When the two separate modules are been synergized together, then this type testing come in the picture. As you can have a look right below this statement, Module A and Module B is been collaborated and hence tested post to the integration.
It can only be performed by the test team or the integration tool for testing
It is been categorized into two approaches which include “Top-Down” and the “Bottom-Up” approach. As you can have a look at the below snap:
Let us learn about its types and techniques:
1. Big Bang integration testing:
In Big Bang incorporation testing all segments or modules are coordinated at the same time, after which everything is tried overall. According to the underneath picture every one of the modules from 'Module 1' to 'Module 6' is incorporated at the same time then the testing is completed
2. Top-down integration testing:
The testing is been configured from Top to Bottom, thus snapping down the structural view of the Top-Down Integration Testing. It is been named as stub…
3. Bottom-up integration testing:
Testing happens from the base of the control stream upwards. Parts or frameworks are substituted by drivers. The following is the picture of 'Base up approach':
Thus, this was about the type of Integration Testing for more details... Kindly visit the following link below:
Cheers!