Bottom Up Integration Testing

An approach to integration testing where the lowest level components are tested first then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

In this approach testing is conducted from sub module to main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module.


* Advantageous if major flaws occur toward the bottom of the program.
* Test conditions are easier to create.
* Observation of test results is easier.


* Driver Modules must be produced.
* The program as an entity does not exist until the last module is added.