What is integration testing? who will perform(white box testors or black box testors?

White box testers

Integration Testing can be done by white box testors( Developers) while developing the software i.e before build .

Integration Testing can be done by Black box Testers (Testers) after Build to test whether any bugs are formed while intergarting (linking one screen to other).

so, I want to conclude that this Intergration testing will be done by both White and Black Box testers.

Ramana.

Hi suji....

Integration testing is nothing but testing two individual unit or the component.

In this testing we will test the data linking and data sharing.

This testing will be done by both developer as well as testers.

They are three techniques in integration testing
1. Top down Approach - Stubs
2. Bottom up Approach - Drivers
3. Big Bang Approach - Both

Integration testing is primarily done to ensure that no data loss happens as the data flows across differnent modules in a System. Integration testing also ensures that end to end transations in any system are working on the desired manner

intergration test is conducted by white box test eningeers or block box test eingers integration testing is conducted on group modules

Integration testing (sometimes called Integration and Testing, abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.

More

Integration testing test the communication b/w units.
Black box tester as well as developers did the integration testing.

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

Hi all
I have tested modules of an application seperately but was never part of integration testing.My current job demands an integration testing part...where the modules I tested once will be integrated and given to me...
So i have the following doubts
1.We will be following Bottom Up appraoch ...but how will I prioritise my testing task??
2.Shall I only need to test the functionalities that get affected.
3.Or shall I need to test the whole application all over again

Help me come out of Confusion

Hi Rose,

What you are saying, you have already tested.

At integration testing, the scope is different and aim is different of the testing.

At integration test whether two modules are communicating well or not, If there is any change in functionality, then test that, otherwise you can avoid it now.

As i know , at integration level there will addition of some new minor functionality so that modules can communicate, keep concentration on that.

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

Thanks brijesh for that quick reply

Could u pls elaborate on this statement "some new minor functionality so that modules can communicate"

Just give me an example if possible so that it becames more clear for me...

See, some times for a module to work, developer put some static data , that have to change dynamically when all modules works together.That you have to test.For ex, there are two module, user registration and form posting,like here.

Now registration module is different, form posting is different, developer makes a static user , who post form to ask questions.

But when it get integrated, the id of user will come from registration module, now there will some change in code, to fetch user id.This type of functionality you should concentrate when test.

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

Thanks brijesh....one more query
So all the stub datas getting replaced by the real time data need to be tested during integration phase...that part is clear for me nw

Secondly..during integration because of the code change usually we say like "other parts may get affected"...How can we recoganize these "Other parts"....Or is it during Exploratory testing that we find out these affected parts??

The other parts that may get affected will be in and around the ‘links’ between individual modules. I am calling the features that involve in synchronization between modules as ‘links’.

The HLD documents will define these links.

HLD is High Level Design

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-

Hi,

We are writing test cases for Integration testing as well as we get the Customers requirements.
What is the difference between them .Please tell me.

thanks
vikas goyal

Who do the Integration Testing. Developer or Tester. According to me it is done by Tester. what your views.

Even in UNIT testing developer performs...but its a responsibility of a Tester

Integration Testing is Test team's responsibility.

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-