Integration Testing

Integration testing:-

After completion of unit testing for each and every module units then programmers are integrating all the modules as a system or software based HLD document .after completion of integration of modules programmers are applying integration test to find out all the modules correctly integrated or not from base module to end module as per HLD document

                 Some times to implement coding for all the modules and to integrated all the modules with in specified for system testing that is not possible for .then programmers are following below types of integration approaches to integrate modules and to perform system testing

• Top down approach
• Bottom up approach
• Hybrid approach
• System approach

Top down approach:-

in this integration some of sub modules under code constructions instead of that sub module programmers are using dummy module called as "STUB" only for integration purpose

Bottom up approach:-

in this integration some of main module is under construction instead of that module programmers are using temporary module called "DRIVER" only for integration purpose

Hybrid approach:-

in this approach programmers are using both "STUB" and "DRIVER" for main module and sub module is called hybrid approach

System approach:-

coding is completed for all the modules at a time then programmers are following this type of integration approach