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.
Steps in Top Down Integration Testing
Top-down testing is a type of incremental integration testing approach in which testing is done by integrating or joining two or more modules by moving down from top to bottom through the control flow of the architecture structure. In these, high-level modules are tested first, and then low-level modules are tested. Then, finally, integration is done to ensure that the system is working properly. Stubs and drivers are used to carry out this project. This technique is used to increase or stimulate the behavior of Modules that are not integrated into a lower level. Processing:
The following are the steps that need to be followed during processing :
Contact Us