Integration testing is a phase in the software development lifecycle (SDLC) where individual components or systems are combined and tested as a group to ensure they work together correctly.

Ensures Component Compatibility – Confirms that different software modules and hardware components function correctly when integrated.

Identifies Data Flow Issues – Ensures seamless communication between software systems, databases, and external applications.

Detects System-Wide Errors – Finds defects that unit testing (individual module testing) may miss.

Prepares for System Testing – Integration testing is conducted before full system testing to ensure subsystems work together as expected.

A. To verify that the application meets stated user requirements.

This refers to User Acceptance Testing (UAT), not integration testing.

B. To verify that standalone programs match code specifications.

This describes unit testing, where individual components are tested separately.

C. To verify that the application would work appropriately for the intended number of users.

This describes performance or load testing, which measures system behavior under high user load.

IIA’s GTAG on IT Risks and Controls – Emphasizes the role of integration testing in ensuring secure and functional IT environments.

COBIT 2019 (Governance and Management of IT) – Recommends integration testing to reduce IT system failures.

ISO/IEC 25010 (Software Quality Model) – Lists integration testing as a key quality assurance step.

Why Option D is Correct?Why Not the Other Options?IIA References: