part of the SIT work segment. It is to verify that the system is working properly with other up-stream and down-stream systems. Its primary purpose is to test interfaces.
Integration testing is undertaken to ensure that components can be integrated to form modules, modules to form subsystems and subsystems to form the system.
The testing of a chain of business processes which flow together and/or cross functional boundaries. Integration testing also involves outputs, interfaces, procedures, organizational design, and security profiles. Its focus is on likely business events and high-impact exceptions.
An orderly progression of testing in which software components or hardware components, or both, are combined and tested until the entire system has been integrated.
Testing performed to expose fault s in the interfaces and in the interaction between integrated component
testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them [ IEEE 90].
Depth testing which covers groups of functions at the subsystem level.
Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.
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.
