Manual_TestingPhases_IntegrationTesting

 Integration Testing/Interconnection Testing/Interface Testing:-
Program1𑁋𑁋interface program𑁋𑁋⋗Program2

• Checking the connection between different screens/factors is called Integration Testing. 

  (or) By developing an Interface Program developer can connect the different programs. Testing this interface program is called integration Testing.

  
  

• This interface program test by the developers and once the application goes to the QA environment QA will also test the interface.
• There are Four different types of integration testing.
• Top-Down Approach
• Bottom-up Approach
• Sandwich Approach
• Big-Bang Approach

    Top-Down Approach:

Main Module (complete)

↙        ↘STUB

↙                 ↘....

Sub 1 (complete)            Sub 2 (in-complete)

• Will start integration from the main module.
• If the main module is completely developed, and the sub-module is not developed then the developer writes STUB code to complete the integration test.
• STUB/CALLED Program:
• It's a temporary code in order to make sure integration testing is complete.
• Example: when we click on an in-completed web page,  that page will be opened but it will show some message like This page is under construction/It will be available very soon ...  

    Bottom-Up Approach:-

Main Module (in-complete)-(DRIVER)

↓

Sub 1 (complete)

↓

Sub 2 (complete)

• In this, integration testing is also like the Top-down approach testing starting from the Main module.
• But here the main module is not developed and sub-modules are developed. then on the Main module developer implement a temporary program called DRIVER. By this test the program from the main module.
• Example: Without writing any content on the Main page, they will just add a button(like a start button) to go from next sub-module

    Sandwich Approach/Hybride Approach:-

Main Module (in-complete)-(DRIVER)

↓    

Sub 1 (complete)

↙          ↘STUB

Sub 2 (complete)        Sub 3 (in-complete)

• It is a combination of both the Top-Down Approach and the Bottom-Up Approach.

    Big-Bang Approach:-

• There is no need for any integration, Once the entire project is done then we do integration testing.