What is Integration Testing:Objective,Type and Benefits

What is Integration Testing:Objective,Type and Benefits

What Is Integration Testing??

Integration testing is performed to check the interactions between different components or systems.

Component integration tests and system integration tests should concentrate on the integration itself. For example, if integrating module, A with module B, tests should focus on the communication between the modules, not the functionality of the individual modules, as that should have been covered during component testing. 
Component integration testing is often the responsibility of developers. System integration testing is generally the responsibility of testers.

Main Objectives of integration testing are:

Ø Building confidence in the quality of the system for this automated regression test could be used.
Ø Finding defects (which maybe in the interfaces themselves or within the components or systems).
Ø Reducing risk.
Ø Verifying whether the functional and non-functional behaviors of the system are as designed, specified and working as per requirement.
Ø Preventing defects from escaping to higher test levels.

Primarily there are two different types of integration Testing:
·      Component integration testing
·      System integration testing

Component integration testing

Main focus in this testing is to validate interactions and interfaces between integrated components. This testing is usually performed after component testing and is generally automated. In iterative and incremental development, component integration tests are usually part of the continuous integration process.

System integration testing

This Testing focuses on the interactions and interfaces between systems, sub-system and packages. System integration testing can also cover interactions with, and interfaces provided by, external organizations (e.g., web services). System integration testing may be done after system testing or in parallel with ongoing system test activities (in both sequential development and iterative and incremental development).

Now the obvious question that comes to our mind was on what basis or documents integration testing could be performed:

Ø Business or System Requirement Documents.
Ø Flow or Sequential Diagrams
Ø Architecture diagram
Ø User Story or Use Cases
Ø Design Specification Documents.

What kind of Issue Can be identified by Integration Testing??

Typical issues that can be identified in integration testing are:

Ø Incorrect data, missing data, or incorrect data encoding.
Ø Inconsistent message structures between different systems.
Ø Incorrect sequencing or timing of interface calls.
Ø Interface mismatch.
Ø Failures in communication between components or systems.
Ø Unhandled or improperly handled communication failures between components or systems.
Ø Incorrect assumptions about the meaning, units, or boundaries of the data being passed between components



My Name is Ankur Jain and I am currently working as Automation Test Architect.I am ISTQB Certified Test Manager,Certified UI Path RPA Developer as well as Certified Scrum Master with total 12 years of working experience with lot of big banking clients around the globe.I love to Design Automation Testing Frameworks with Selenium,Appium,Protractor,Cucumber,Rest-Assured, Katalon Studio and currently exploring lot in Dev-OPS as well. I am currently staying in Mumbai, Maharashtra. Please Connect with me through Contact Us page of this website.

Previous Post
Next Post