Sunday, 11 October 2015

Top-down Integration testing

Top-down Integration testing this approach when lower level components are developed they are integrated with highest level components. It is known as top down or top to bottom approach. Top-down integration testing mainly needs for the testing team to identify what is important and what is least important modules, then the most important modules are worked on first. In this approach there is a possibility that a lower level module is missing or not yet developed which affect the integration between the other modules. Top Down approach is like a Binary tree where testing starts from top to roots.
In this situation to make the integration possible developer develop the temporary dummy program that is utilized in place of missing module known as ‘STUB’ for the smooth running of integration testing.
In Top-down Integration testing approach the decision making occurs at the upper level in the hierarchy and encountered first. The main advantage of the Top Down approach it is easier to find a missing branch link.
The problem occurs in this hierarchy when processing the lower level components to adequately test highest levels. As stubs are used to replace lower level components at the beginning of top down approach; no significant data can flow between the modules. Lower level modules may not be tested as thoroughly as the upper level modules.
Top down Intergration testing
Top-down Integration testing

No comments:

Post a Comment