Is integration testing is related to developer or tester

If any one knows please clarify

It is related to developper...i suppose....Regression testing is the corresponding testing term..

Maximum the Integration testing is done by the developers only.
But in some rare cases testers will do the Integration Testing.

According to me both does the integration testing.

But both have different view at the time of testing.

Hi

There will be a separate team in every organization and they perform integration testing.

[QUOTE=dorababu nellore;17002]Hi

There will be a separate team in every organization and they perform integration testing.[/QUOTE]

No, not at all.

It's not true.

It may be for MNC's and big companies, but not for all.

I agree to the fact that Integration Testing is done by developers however in certain cases Testeing Prosffessionals may be asked to check the functionality of the System during Integration Testing.

I would say, it depends on the structure of the organization..

By the way,
1) Can some one explain what is the best definition of integration testing with some examples ?

Or

2) What is the difference between the integration testing and interface testing ?

Thanks & Regards
Dhruva

integration testing is done by test team.

[QUOTE=dhruva101;17176]I would say, it depends on the structure of the organization..

By the way,
1) Can some one explain what is the best definition of integration testing with some examples ?

Or

2) What is the difference between the integration testing and interface testing ?

Thanks & Regards
Dhruva[/QUOTE]



Hi ,

1) "Integration testing can be defined as the phase where in all individual software modules are combined and tested as a group. It follows unit testing and precedes system testing."

2) Interface Testing is not focussed on what the components are doing but on how they communicate with each other, as specified in the "System Design". The "System Design" defines relationships between components, and this involves stating:
[LIST][*]What a component can expect from another component in terms of services. [*]How these services will be asked for. [*]How they will be given. [*]How to handle non-standard conditions, i.e. errors.[/LIST]
Tests are constructed to deal with each of these.
The tests are organised to check all the interfaces, until all the components have been built and interfaced to each other producing the whole system.

There is no major difference between Integration and interface testings
but integration testing is the phase which comes immediately after coding is done for all the modules of one component. which is usually done by developers and disign engineers its a white box testing.
But, Interface testing is done after all the major componets of a system are ready and passed unit testing.

For Example assume that we are building a mobile application in which we have 3 major componets which are developed using three different technologies like windows mobile , J2ME, and managed c++.
Now when we develop individual componets module by module we use Integration testing in later stage when we test all the components together we use Interface Testing becoz when we use different technologies in same application the probability of interface issues wil increase

I agree to your explanation and would like to add more to that. Integration testing need not to be a combination of modules. It could be the sharing the same database between two applications.

In our shop, there are certain DB2 tables and these tables are updated and used multiple systems. When any one system enhances their application that invloves updating common tables, they have to have intimate understanding the other systems with respect to the usage of the commom tables.

Each group does their testing though one group didn't have any changes to
their application but making sure that their functionality is intact due to the changes to DB2. You can call this as integration testing or even a regression testing for other group.


Interface testing: Two different applications residing either on the same platform or differrent but connected by a file or some other mechanisam.
Here one application just sends the file based on the agreed format but does not care how the other application uses it.

Integration testing Belongs to Tester ONly...

Devloper is responsible for only UNIT/ MODULE testing...

Application as a whole will be integrated and set up with Simulation environment and shoudl be tsted by tester as a part of INTEGRATION testing...

Unit Testing and Integration testing will be done by the developers, once these testings are completed the product will be released to the testing team for System testing.

In my perspective integration testing is done by the person who is responsible for the functionality. This functionality could be divided into many smaller function and handed over to a developer for the code development. Finally when each of these tasks are over each of this task is done by either the module lead though will be a developer but with higher responsibility of module

As per my knowledge, integration testing is done by a developer.

[QUOTE=jainbrijesh;16985]According to me both does the integration testing.

But both have different view at the time of testing.[/QUOTE]

I have slight disconnect with this reply. As far System testing is concerned as it is a black box testing the test cases doesn't specifically say that this the boundary condition for this functionality and these are the test cases to test these boundary condition. Here rather what you script out are the steps to perform the functionality irrespective of how it interacts ..

Where as Integration testing means you pass certain boundary condition parameters to see if you are getting the expected results .. As a whole in functionality these results could take different results before being show to user...

Hope you are clear with the above statements....

hi all

this is done by both developers and testors
but the scenario is a bit different.....


[B]Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists. Test department coders develop code test scenarios and exercises that will test new units of code after they have been written. These test cases form what becomes the test bucket. Before a new version of a software product is released, the old test cases are run against the new version to make sure that all the old capabilities still work. The reason they might not work is because changing or adding new code to a program can easily introduce errors intocode that is not intended to be changed.[/B]

[B]now the scenario of small companies
there it is done by developers or better to say all type of testings r done by developers there due to economic reasons[/B]

Hi

As per the testing standards INTIGRATION TESTING to be done by Developers only.

> It is kind of white box (Have get involved with code repair also)
> Flow of the modules, and integrating in sequece will be done by coding

So 99% of the organizations will prefer this test by developers only

[QUOTE=satyachakri81_b;16871]If any one knows please clarify[/QUOTE]

integration testing is related to testers during system testing.
During development the developers may have a unit testing and intigratin testing to make sure the development is ok or not. but testers are to certify the result officially.

Integration testing is nothing but testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Integration testing is testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems

a long debate I guess.

It definitely depends on the organizational structure.
[B]At developer side[/B]: Once the modules/submodules are done they will integrate all of them making into a build and release this to the Testing Team. But prior to this the integrator(the person who has been assigned with this task) will test the integration done by him.

[B]At Tester's End:[/B]
The Tester who exactly recieving the build/one performing the smoke test will also check the build as per the integration norms.

But some companies do have their own Integration Team if they have large number of integrations to be done(may be frequently). If such a team exists, then the Team is included with a Tester also whose prime job is to do Integration Testing.

Integration testing is performed by testers` and unit testing is done be developers.