Integration in software testing

In fact, if the top two levels of program structure are integrated top-down, the number of drivers can be reduced substantially, and integration of clusters is greatly simplified.

Integration follows the pattern illustrated below. Note: If the top two levels of program structure are integrated Top-down, the number of drivers can be reduced substantially, and the integration of builds is greatly simplified. In this approach, all modules are not integrated until and unless all the modules are ready.

Once they are ready, all modules are integrated and then its executed to know whether all the integrated modules are working or not. In this approach, it is difficult to know the root cause of the failure because of integrating everything at once. Also, there will be a high chance of occurrence of the critical bugs in the production environment. Skip to content. Example Template What is Security Testing? Report a Bug. Previous Prev. Next Continue.

Home Testing Expand child menu Expand. SAP Expand child menu Expand. Web Expand child menu Expand. The main purpose of this testing method is to expand the process and validate the integration of the modules with other groups.

It is performed to verify if all the units operate in accordance with their specifications defined. In Software testing, it is important that every system component gets integrated with the different application modules. Though each of the software modules is unit tested, there are critical chances for the modules to have defects, and this calls for the need for Integration testing to come into place. Significantly, system integration testing is taken up to effectively verify the various interactions between modules and also verifies the low-level and high-level software requirements as given in the software requirements specifications document.

The need for Integration testing can be understood from the points listed below:. Integration testing is a simple extension of unit testing. With integration testing, most of the test cases are written at the early stage and thus helps to perform execution on every build.

This testing process tackles the bugs related to exception handling and validates the performance, functionality, and reliability of the integrated modules. It is classified into different testing approaches , some of them are:. In this approach, almost all of the units or major units are combined together to perform integration testing in one attempt. Usually, this method is practised when teams have entire software in their bundle.

In this testing approach, a minimum of two modules that are logically related is tested. Then, the related modules are summed up to perform testing and achieve proper functioning. This process is continued until the modules are addressed and tested. In this testing approach, the teams test the top-level units first and then perform step-by-step testing of lower-level units. In this testing approach, the testing starts from the lower units of the application and then gradually moves up, i.

This approach is also known as hybrid integration as it is a combination based on bottom-up and top-down approaches. This approach overcomes many other limitations and helps to achieve the benefits of both the approaches with its three layers: — The main target layer, — The layer below the target layer, and — The layer above the target layer.

After having known about Integration testing in detail, businesses should also know the most important aspect of Steps to Perform Integration Testing. This integration testing uses test drivers to drive and pass appropriate data to the lower level modules. Skip to content. Change Language.

Related Articles. Introduction of Software Engineering. Software Requirements. Software Testing and Debugging. Table of Contents. Improve Article. Test Drivers are needed to simulate higher level units which may not be available during the initial phases.

Integration Testing. ISTQB Definition integration testing: Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also c omponent integration testing, system integration testing. Electronic Data Interchange, Internet. Table of Contents.