Shortcomings of Top Down Integration Testing
Following are some of the logical problems that might arise in top-down integration testing :
- Upper models or high-level modules should be tested properly to maintain quality and for processing lower-level modules or stubs of top-down testing.
- As we know in this type of pf testing, stubs temporarily replace a lower-level module, but data do not move upwards with this replacement. Due to this, testing cannot be done on time which results in delays in testing.
- Due to replacement, stubs might become more and more complex after each replacement.
- Losing control over correspondence between specific tests and specific modules is the main problem that might arise during process.
- Sometimes, modules at lower levels are tested inadequately (unsatisfactory that lacks quality).
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