A Mobile Application Testing Community
Integration testing is an intermediate stage between modular testing and system check-up. In the process of software testing are arranged and studied in complex. As a rule, smaller modules are integrated into bigger ones. The purpose of such integration of several modules into one group is to check whether these units meet functional and acceptance criteria. The testing itself is done with the help of the so-called “Black box” method when there’s no access to product’s source code.
Pretty often, integration testing is compared to modular testing which helps to assess the correct performance of separate modules of product’s code. The difference between modular and integration testing lies in their goals, and, as a result, in the methods they’re carried out with.
Thus, when we do integration testing, the emphasis is made on the analysis of interaction among interface objects. Such integration testing is done on two levels: component and system ones. The first level, component level, assesses system components behavior by the results of component testing. Accordingly, on a system level a testing specialist checks interaction among the systems by the results of system testing. As a rule, two ways of merging modules in groups are singled out:
Incremental way has two approaches to modules merging:
The results of integration testing can show mistakes in the process of module merging. In order to avoid them, a test plan if testing separate modules is made. After testing separate modules, they can be merged based on the peculiarities of their testing.