Integration testing is used to test two or more modules that are unit tested together as a group. There are four types of integration testing:
Bottom-up testing is a type of integration testing that integrates modules from the bottom first and then moves upward in the control flow graph until all modules are tested. Bottom-up testing is also called inductive reasoning.
Driver is a temporary module that is used to call the interface procedures of the module to be tested and report the results. Drivers are used in bottom-up testing to simulate the caller module for a module to be tested.
Disjoint subsystems can be tested simultaneously.
Useful for integration testing of object-oriented systems, real-time systems, and systems with strict performance requirements.
Lower modules can be tested even if their caller modules are not developed yet using drivers.
If a large number of subsystems exist at the same level, bottom-up testing becomes similar to big-bang testing.
The whole system integrated together is tested last.
Driver modules are needed.
Consider the control flow graph of a system shown below:
The integration testing of the system shown above using the bottom-up approach will be as follows:
Consider the control flow graph of a system shown below:
The integration testing of the system shown above using the bottom-up approach will be as follows:
Free Resources