 | This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) (Learn how and when to remove this message)
|
System integration testing (SIT) involves the overalltesting of a completesystem of manysubsystem components or elements. The system under test may be composed of electromechanical orcomputer hardware, orsoftware, or hardware withembedded software, or hardware/software withhuman-in-the-loop testing. SIT is typically performed on a larger integrated system of components and subassemblies that have previously undergonesubsystem testing.
SIT consists, initially, of the "process of assembling the constituent parts of a system in a logical, cost-effective way, comprehensively checking system execution (all nominal and exceptional paths), and including a full functional check-out."[1] Following integration, system test is a process of "verifying that the system meets its requirements, andvalidating that the system performs in accordance with the customer or user expectations."[1]
Intechnologyproduct development, the beginning of system integration testing is often the first time that an entire system has been assembled such that it can be tested as a whole. In order to make system testing most productive, the many constituent assemblies and subsystems will have typically gone through a subsystem test and successfully verified that each subsystem meets its requirements at the subsystem interface level.
In the context ofsoftware systems andsoftware engineering,system integration testing is a testing process that exercises a software system's coexistence with others. With multiple integrated systems, assuming that each have already passed system testing,[2] SIT proceeds to test their required interactions. Following this, thedeliverables are passed on to acceptance testing.[clarification needed]
Forsoftware SIT is part of thesoftware testing life cycle for collaborative projects. Usually, a round of SIT precedes theuser acceptance test (UAT) round. Software providers usually run a pre-SIT round of tests before consumers run their SIT test cases.
For example, if an integrator (company) is providing an enhancement to a customer's existing solution, then they integrate the new application layer and the new database layer with the customer's existing application and database layers.After the integration is complete, users use both the new part (extended part) and old part (pre-existing part) of the integrated application to update data. A process should exist to exchange data imports and exports between the two data layers. This data exchange process should keep both systems up-to-date. The purpose of system integration testing is to ensure all parts of these systems successfully co-exist and exchange data where necessary.[citation needed]
There may be more parties in the integration, for example the primary customer (consumer) can have their own customers; there may be also multiple providers.[citation needed]
