Integration Testing
Integration testing verifies that components or systems interact correctly after being combined into a larger solution.
“A test level that focuses on interactions between components or systems.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Integration Testing?
Integration testing focuses on interfaces, communication, and data exchange between integrated components to identify defects that cannot be detected during isolated testing.
Component interaction: Individual units are tested together after component testing.
Interface validation: Data and control flow between modules are verified.
Defect detection: Reveals integration issues such as incorrect interfaces or communication failures.
Real World Example
An insurance claims platform is connecting a claim intake service, a policy validation service, and a payment approval service.
Each part can look correct in isolation while the handoff between parts still fails. Integration testing helps testers focus on the boundary where data, timing, and responsibility meet.
The tester checks payloads, error handling, retries, missing fields, and the order of service calls instead of only confirming that each screen appears.
The claims flow becomes more dependable because Integration testing exposes defects that only appear when real components collaborate.
Practice Questions
Question 1
Which statement BEST describes Integration testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Integration testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Integration Testing. Test your understanding with topic-specific questions in our Mock Exams.