Integration testing

Who is resposible for integration testing?

Questions by rekha.ga

Editorial / Best Answer

surendra_kumar  

  • Member Since Nov-2006 | Jun 11th, 2008

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.

 

Showing Answers 1 - 66 of 66 Answers

surendra_kumar

  • Jun 10th, 2008
 

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.

 

singamraju

  • Jun 17th, 2008
 

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.

naresh.testingg

  • Jul 4th, 2008
 

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.

  Was this answer useful?  Yes

876manu

  • Aug 27th, 2008
 

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.


Mandeep Sharma

santy7in

  • Sep 1st, 2008
 

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.

  Was this answer useful?  Yes

qawer

  • Sep 26th, 2008
 

Integration testing should be completed by developers. When developer finish programming all the modules, the developer should do the test in developing environment to check if the application works or not. After that the developing team would pass the application with all the modules to the QA team for functional test or regression test.

  Was this answer useful?  Yes

vanikg

  • Jan 16th, 2009
 

Both developer & tester are responsible for Integration Testing. Developer needs to do initial level of testing like after integration of models whether it is working properly according to SRS without any major issues like throwing exceptions etc after developer makes sure that software is testable, handle it over to the tester. Now real tester responsibility starts to break the software. Before that testers must be prepared with different testing scenarios. It will be good if testers have idea of database to identify the proper flow of data in database.

  Was this answer useful?  Yes

lopamudra das

  • Jan 18th, 2009
 

Tester alone can't be responsible for integration testing. Ideally developer only responsible for integration testing. In few companies integration testing is done by both developer and testers. in that case we can say that in integration testing both developer and tester is responsible.

  Was this answer useful?  Yes

srinivasulub1981

  • Feb 3rd, 2009
 

As for me there would be no rules as this should be tested by tester/dev only, i believe this is a mutual understanding between dev and tester.

So while Ingegration the modules it self developer can do the unit testing up to some extend, after they passed the application to QA, now QA need to do the complete round of testing? on all modules.

Srinivas

  Was this answer useful?  Yes

nag786

  • Feb 6th, 2009
 

Integration testing is nothing but to prove that the combined parts of the developed system works fine and they are collective working fine and making sure that interfaces between the integrated modules are also working fine.

Making sure that the integrated modules yielding the results what customer expecting from the combined/ whole system/ Application.

  Was this answer useful?  Yes

nag786

  • Feb 6th, 2009
 

Both Developer and Tester are responsible for this type of Testing

Intergation Testing is Nothing but combining the individual modules and testing to ensure that these modules work properly and collectivly fine and their interface are also working fine.

Nagaraja Goud Emagowda

  Was this answer useful?  Yes

vk1978

  • Feb 20th, 2009
 

Test team is responsible for over all Quality of the project, without acceptance of test team project cant be installed at client's environment and Integration Testing is a part of Testing

  Was this answer useful?  Yes

ankushsingh

  • Jun 28th, 2009
 

Integration testing testing is responsible to check the integration points of the application. Here we check the flow of the data from one module to another is proper and integration of the module is proper or not.

  Was this answer useful?  Yes

manii17k

  • Oct 13th, 2010
 

Don't worry about integration testing but u need to have idea about tht basically integration testing is done by white box test engg (developers )but as a black box test engg u need to have that idea .

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions