When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.
Integration Testing takes as input units which are testing in Unit Testing and group them in large modules and test them then provide the output to the System Testing. Integration Testing Perform by Test Team. This is the Black Box Testing type.
The purpose of Integration Testing is to verify the Functionality, Performance and the Requirement based on the design phase.
1) Big Bang: In this approach, most of the modules which are developed connected together to make the complete software and tested. This approach is very time saving approach. If Test Cases are not reported properly then the process is more complicated to understand and it is very tough for the testing team to achieve the goal of Integration Testing.
2) Top Down Integration Testing: The Top Down Integration approach will work when some lower level modules are not completed and Team team need to perform the Integration Testing. For this we use the stubs which are the temporary program to replace with the uncompleted modules to complete the Integration Testing.
In Top Down Integration Testing, testing start from the top level and continuous with the lower level to test the Integration. Top Down Integration Testing also called the Incremental Approach.
3) Bottom Up Integration Testing: The Bottom Up Integration Approach start from the bottom and carried to top of the software. In this hierarchy, the top level are substituted with the Driver which are temporary program to replace with the uncompleted code.
In this testing, Lower level of modules are tested first then higher level component tested. Top Down Integration Testing also called the Incremental Approach.
4) Sandwich Testing: In this approach, team combine both Bottom up and Top down approach.
Integration Testing takes as input units which are testing in Unit Testing and group them in large modules and test them then provide the output to the System Testing. Integration Testing Perform by Test Team. This is the Black Box Testing type.
The purpose of Integration Testing is to verify the Functionality, Performance and the Requirement based on the design phase.
Type of Integration Testing
1) Big Bang: In this approach, most of the modules which are developed connected together to make the complete software and tested. This approach is very time saving approach. If Test Cases are not reported properly then the process is more complicated to understand and it is very tough for the testing team to achieve the goal of Integration Testing.
2) Top Down Integration Testing: The Top Down Integration approach will work when some lower level modules are not completed and Team team need to perform the Integration Testing. For this we use the stubs which are the temporary program to replace with the uncompleted modules to complete the Integration Testing.
In Top Down Integration Testing, testing start from the top level and continuous with the lower level to test the Integration. Top Down Integration Testing also called the Incremental Approach.
3) Bottom Up Integration Testing: The Bottom Up Integration Approach start from the bottom and carried to top of the software. In this hierarchy, the top level are substituted with the Driver which are temporary program to replace with the uncompleted code.
In this testing, Lower level of modules are tested first then higher level component tested. Top Down Integration Testing also called the Incremental Approach.
4) Sandwich Testing: In this approach, team combine both Bottom up and Top down approach.
Comments
Post a Comment