Introduction to Integration Testing

Integration test, English is integration testing.

Integration testing refers to the joint testing of individual components of an application system to determine whether they can work together without conflict. A part can be a block of code, a standalone application, a client on a network, or a server-side program. This type of testing is especially relevant to client servers and distributed systems. Before the general integration test, the unit test needs to be completed.

Integration testing is a logical extension of unit testing. Its simplest form is: Two tested units are assembled into one component, and the interfaces between them are tested. In this sense, a component refers to an integrated aggregation of multiple cells. In a real-world scenario, many units are assembled into components that are then assembled into a larger part of the program. The method is to test the combination of fragments and eventually extend the process to test your module with the other group's modules. Finally, all modules that make up the process are tested together. In addition, if a program consists of multiple processes, you should test them in pairs instead of testing all the processes at the same time.

Integration testing identifies problems when combining units. By using a test plan that requires testing each cell before the composition unit and ensuring the viability of each unit, it is possible to know that any errors found in the composition of the unit are likely to be related to the interface between the cells. This approach reduces the number of possible scenarios to a simpler level of analysis.