Hi,

Top down : testing hierarchy starts from higher level to lower level. if suppose testers dnt get the lower modules for testing (consider the lower modules are under developmnt) what the testers will do they wil place dummy modules and integerate these dummy modules with the higher level modules. In top down apparoach the dummy modules are called Stubs.


Stubs- Def:- Stubs are the dummy modules tht simulates the low level modules. Stubs are called Functions.


Bottom up: testing hierarchy starts from higher level to lower level. if suppose testers dnt get the higher modules for testing (consider the higher modules are under developmnt) what the testers will do they wil place dummy modules and integerate these dummy modules with the lower level modules. In this Bottom up apparoach the dummy modules are called drivers.

Drivers- Def::- Drivers are the dummy modules that simulate the high level modules. Drivers are calling Functions.

Regards,
Narendra.

Hi,

In Top-down integration The core module(Main Module) is developed first and In order to test this Core module we develop dummy smaller modules called 'Stubs'. These stubs are small codes to test the functionality of the core
module.

Mostly Developers and Unit Testers will do the integration testing.

Integration tests are for procedural languages. This is easily generalized for OO languages by using the equivalent constructs for message passing. In the following, the word "call" is to be understood in the most general sense of a data flow and is not restricted to just formal subroutine calls and returns ? for example, passage of data through global data structures and/or the use of pointers.

For Ex:-

Let A and B be two components in which A calls B.
Let Ta be the component level tests of A
Let Tb be the component level tests of B
Tab The tests in A's suite that cause A to call B.

Tbsa The tests in B's suite for which it is possible to sensitize A -- the inputs are to A, not B.

Tbsa + Tab == the integration test suite (+ = union).

Hope this is clear..

Regards,
Narendra.

hey,bottum up integration starts from lower level to higher level i.e. from

bottum to top...

Hi tirru,

Integration testing is a testing methodology where we test the interfaces between components, interactions to different parts of a system such as operating system, file system and hardware or interfaces between systems.

Integration testing can be done in such a way that all programs are integrated one by one, and a test is carried out after each step. It is called as incremental approach of doing integration testing. It can be of two types :-
1) Top-down : Here testing starts from the top module (main module) and ends at the bottom module (Sub menu module) and integrated one by one. If any sub module is not ready then a dummy of that module is prepared which is termed as stubs and then that sub module is substituted by stubs.

2) Bottom-up : Here testing starts from the bottom module (Sub menu module) and ends at the top module (Main module) and integrated one by one. If main module is not ready then a dummy of that module is prepared which is termed as drivers and then that main module is substituted by drivers.

Regards
Sitam