Integration Testing

html5 and css3

Integration Testing

In Integration testing method, individual software modules are taken and combined and tested as group. Integration testing done after unit testing. Integration testing identifies the issues in the interfacing between modules.

Integration testing is a software testing technique that focuses on verifying the interactions and communication between different components or modules of a software system. The objective of integration testing is to identify defects or issues that may arise when integrating multiple units together.


  • Integration testing improves the quality of the code
  • It allows the programmer to refactor code or upgrade system libraries
  • Integration testing reduces defects in the newly developed features or reduces bugs when changing the existing functionality
  • Integration testing helps reduce the cost of bug fixes
  • Integration testing provides documentation of the system
  • Integration testing occurs after unit testing and before system testing in the software testing life cycle (STLC).
  • The primary purpose of integration testing is to validate the interface contracts and interactions between components.
  • In this approach, all the components are integrated and tested together at once.
  • This approach involves testing the higher-level components first, simulating the behavior of lower-level components using stubs or mock objects.
  • Integration testing can be performed in various test environments, including dedicated integration test environments, staging environments, or even production-like environments.
  • Integration testing requires suitable test data that covers different scenarios and input combinations to exercise the integrated components thoroughly.
  • Integration testing involves managing dependencies between components effectively.
  • Integration testing focuses on testing error handling and exception scenarios when components interact.
  • Integration testing plays a vital role in continuous integration (CI) practices.
  • Validating the integration between the application and the database, including data consistency, data retrieval, and data manipulation operations.

Why Integration Testing?

Integration testing, especially test driven development, is a design or implementation activity, not a testing activity.

Integration testing helps identify integration-related defects, such as incompatible interfaces, data inconsistencies, communication failures, or incorrect behavior when multiple components interact. It ensures that the system functions correctly as a whole and provides confidence in the overall quality and reliability of the software application.