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.
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 the phase of software testing in which the the individual software modules are combined and tested as a group.The main objective of integration testing is to see the side effects after integrating all the individual modules.It follows Unit testing and preceeds System Testing...
Integration Testing comes under White Box Testing after testing individual units in unit testing all of them should be tested for working in integration with each other Integration Testing can be done with different methods e.g Top-Down Bottom-Up and Sandwitch Testing user can use Stubs(Sub-Modules) and Drivers(Parent Module) for integration Testing.It is a middle layer of testing between Unit and System testing.
Integration Testing comes under White Box Testing after testing individual units in unit testing all of them should be tested for working in integration with each other Integration Testing can be done with different methods e.g. Top-Down Bottom-Up and Sandwitch Testing user can use Stubs (Sub-Modules) and Drivers (Parent Module) for integration Testing. It is a middle layer of testing between Unit and System testing.
