Advantages Top Down Integration Testing

Steps of Top-Down Integration Testing

The test driver represents the main control module also known as a high-level module and stubs are generally used for all low-level modules that directly subordinate (present or rank below another) to high-level modules. In this, testing takes place from to bottom. So, too, high-level modules are tested first in isolation. After this, low-level modules subordinated modules, or stubs replace high-level modules one by one at a time. This can be done using methods like depth-first or breadth search. The process is repeated until each module is integrated and tested. Another stub replaces the present real or control module after the completion of each set of tests. These stubs act as s temporary replacement for a called module (stubs) and give the same result or output as the actual product gives. To check if there is any defect or any error occurred or is present, regression testing is done and it’s important to reduce any side effects that might be caused due to errors that occurred....

Shortcomings of Top Down Integration Testing

Following are some of the logical problems that might arise in top-down integration testing :...

Example of Top Down Integration Testing

In the top-down integration testing, if the depth-first approach is adopted then we will start integration from module M1. Then we will integrate M2, then M3, M4, M5, M6, and at last M7....

Advantages Top Down Integration Testing

There is no need to write drivers. Interface errors are identified at an early stage and fault localization is also easier. Low-level utilities that are not important are not tested well and high-level testers are tested well in an appropriate manner. Representation of test cases is easier and simple once Input-Output functions are added....

Disadvantages Top Down Integration Testing

It requires a lot of stubs and mock objects. Representation of test cases in stubs can be not easy and might be difficult before Input-Output functions are added. Low-level utilities that are important are also not tested well....