Integration testing is testing software after integrating 
all the modules to ensure that it is working according to 
the specified functionality.

Stubs:Temporary programs used in place of sub modules.
Driver:Temporary program used instead of main module.

Types of integration:1)Top- down 2)bottom-up 3)Hybrid 

If u need more information please find it over 
(www.google.com).

Regards,
Srini

Integration testing is testing software after integrating 
all the modules to ensure that it is working according to 
the specified functionality.

Stubs:Temporary programs used in place of sub modules.
Driver:Temporary program used instead of main module.

Types of integration:1)Top- down 2)bottom-up 3)Hybrid 

If u need more information please find it over 
(www.google.com).

Regards,
Srini

Integration testing is testing software after integrating 
all the modules to ensure that it is working according to 
the specified functionality.

Stubs:Temporary programs used in place of sub modules.
Driver:Temporary program used instead of main module.

Types of integration:1)Top- down 2)bottom-up 3)Hybrid 

If u need more information please find it over 
(www.google.com).

Regards,
Srini

Integration testing is testing software after integrating 
all the modules to ensure that it is working according to 
the specified functionality.

Stubs:Temporary programs used in place of sub modules.
Driver:Temporary program used instead of main module.

Types of integration:1)Top- down 2)bottom-up 3)Hybrid 

If u need more information please find it over 
(www.google.com).

Regards,
Srini

Testing combined parts of an application to determine if 
the fucntion together correctly.The parts can be code 
module,Individual applications etc.

Stub:--is a dummy procedure module or unit that stands in 
an unfinished portion of a system.Mostly used with Top-Down 
Testing

Driver:--is supporting code or data used to provide an 
enviroment for testing part of a system in isolation.

Thanks
Rohit Gahlaut
rsgahlaut@yahoo.com

we can simply say that, interface between the other module
or screen called an integration testing. In our integration
testing we can normally classified into two types.

1. Top - down integration testing
2. Bottom-up integration testing.

But , most of the projects, they will go for only on a
Bottom-up approaches, y because each dev will take care of
an single module and later point of time they will combaine
one by one.. that will be good approaches too.. 

Stubs:  Programs used in place of sub modules ( bottom-up)
Driver:  program used instead of main module. ( Top-down)