it is not just the developer OR the Tester is responsible for integration testing, Both of them are equally responsible according to their responsibilities. The developer who writes the code is responsible for performing the integration of modules w.r.t. code ( should be understood as part White Box Testing ) Then after checking the modules for their integration it will be passed on to the Q.A. team, Here it will be the responsibility of the Q.A. team to check the integration b/w the modules according to the requirement specifications.
Different approaches ofIntegration testing process done by Qa Tester in real environment
I have done lot of integration testing in Rent A Center and colonial bank to check whether the combined parts of an application working correctly or not.In Rent A Center as we are dealing with financial database,To convert DTS to SSIS package..I attended Design phase meeting and walk through meetings to find out How each component in database integrated ,So that I can have clear picture about the Bulid of Our application. We did Integration testing parallel to the component development as it saves lots of our time in testing.With this project I gained experience that we can’t do integration testing on Entire component as it takes 1) longer to locate Faults 2)End results takes more time . That’s the reason we preferred to go for Incramental Integration testing by checking each component Seperately,The advantage we had are Easy fault location,easy recovery from Disaster problems in our financial Data base.I have done lot of Bottom approach integaration,Top Down integration and Thread integration in my previous projects.Gained familiarity with Stubbs.After Converting the package in to SSIS we did integration testing to check whether the new package has any kind of effect on Data base ,Whether it can work on different browsers and navigators other than Windows application. With this experience I conclude that Integration testing plays vital role in any application or project ,As we need to do Integration testing from Design phase to Implementation phase.
Combining all the modules to make one software is known as integration testing. In these they are four types they are 1. Bottom up approach 2. Top down approach 3. Hybrid approach. 4.System approach.
Testing and developer, both teams are equally responsible for the Integrated testing.
The reason for both are given below:
Developer: when they build the application they also need other application on which his own application is depend. When they test their application they also need a proper result from other depended application. So this developer is responsible for the Integrated testing.
Tester: Either developer do the integrated testing or not. Tester need to test or cross the check all the dependency with other modules. If he doesn't do this then it gives the error at client side and they ask testing is not done completely. So the tester is also responsible for the integrated testing.
If you see broadly complete project team is responsible for Integration testing.
Different team will develop different modules and the integration team (Developers) will integrate and sends it for testing.
Finally Testing team will check for interfaces, UI, functionality of the application.
In case if any modules are pending then that corresponding team will prepare Mock objects and sends it to integration team(Developers) or Integration team itself will developer Mock objects.
1 
1