Integration testing
Integration testing checks that software modules and systems work correctly together. We test the interfaces, data flow and API contracts between components, so defects in the connections are found before system testing.
Four integration approaches
- Big bangSmall systems
- Top-downUI first
- Bottom-upCore first
- Sandwich (hybrid)Large systems

Reviewed by Tudor Brad, Founder & CEOISTQB Certified Tester (Foundation Level) · Engineering degree, Technical University of Cluj-Napoca · Completed the DNSC-authorised Cybersecurity Auditor programme (2026) · Certified trainer
What is integration testing?
Integration testing focuses on interactions and interfaces between components or systems. It verifies that integrated units work correctly together, validating data flow, API contracts and communication between components.
This test level sits between component testing and system testing, and finds interface defects before they reach system-level testing.
The ISTQB definition
ISTQB defines integration testing as a test level that focuses on interactions between components or systems. It names two kinds: component integration testing, between parts of one system, and system integration testing, between your system and others, such as third-party services and APIs.
Integration approaches
| Approach | How it works | Best for |
|---|---|---|
| Big bang | All components are integrated at once and tested as a whole. Simple, but hard to isolate faults when something breaks. | Small systems |
| Top-down | Testing starts with the top-level modules and works downward, using stubs for lower modules not yet integrated. | UI first |
| Bottom-up | Testing starts with the lower-level modules and works upward, using drivers to stand in for higher modules. | Core first |
| Sandwich (hybrid) | Combines top-down and bottom-up, integrating from both directions at once. | Large systems |
Contract testing between services
Contract testing is a type of integration testing that checks services can communicate and that the data they share follows an agreed set of rules (ISTQB CTAL-TAE 5.1.3). It extends the two integration levels in the ISTQB Foundation syllabus, component integration testing and system integration testing.
- Consumer-driven: each consumer states what it expects from the provider, and the provider is tested against those expectations.
- Provider-driven: the provider publishes the contract and consumers are checked against it.
Where it sits next to integration testing: integration tests prove the services work together in a running environment. Contract tests check each side against the stored contract on its own, so they run without every service being up and a provider change that would break a consumer fails the build. They complement a small set of end-to-end tests rather than replace them (ISTQB CTAL-AT 1.2).
Integration testing process
Interface analysis
Identify every integration point, API, data contract and protocol between components or systems.
Approach selection
Choose big bang, top-down, bottom-up or hybrid, based on the architecture and project constraints.
Test design
Write tests for interface behaviour, data flow, error handling and contract compliance.
Environment setup
Configure the environment with the stubs, drivers, test databases and service mocks it needs.
Execution and analysis
Run the tests, watch the interactions, analyze failures and confirm the contracts hold. Failures can also hide in what an interface says back: in one API invalid requests got a 200 and a success flag, in four different subsystems.
Key benefits
Early defect detection
Finds interface and integration defects before system testing, when they are easier to isolate and cheaper to fix.
Interface validation
Confirms that interfaces, API contracts and data exchange work as designed when components are put together.
Risk mitigation
Validating integration points early prevents cascading failures when the full system is assembled.
Continuous integration
Supports small, frequent integration in CI/CD pipelines instead of one risky big bang at the end.
Integrating a third-party service?
Those contracts change without warning. We test for that. Talk to us
ISTQB certification alignment
Foundation level certification
Our integration testing follows ISTQB Foundation Level principles for test levels, integration strategies and interface testing techniques. We use the standard definitions of big bang, top-down, bottom-up and hybrid integration from the ISTQB Glossary.
View the ISTQB integration testing definition. For REST APIs and microservices, see our API testing page.
How BetterQA does integration testing
We test the connections between your systems: REST APIs, microservices and databases, with Postman, REST Assured and contract tests, and run them in your pipeline so a broken contract fails the build.
Engineers who test for a living
50+ QA engineers, working since 2018. People plan and run the integration testing and report what the results mean for your release.
Bugs you can act on
Every defect we find is written up in BugBoard, our own test management tool, or in your tracker, with steps to reproduce, the expected and actual result, and the environment.
A certified process
ISO 9001 for quality management and ISO 27001:2022 for information security. See our certifications.
How an engagement works
- €20-45 per hour
- First month is a trial
- First two weeks complimentary if you are not happy
- 30 days notice after that

Integration testing: common questions
What is integration testing?
A test level that checks the interactions and interfaces between components or systems: data flow, API contracts and communication between integrated units.
What is the ISTQB definition of integration testing?
ISTQB defines it as a test level that focuses on interactions between components or systems, and splits it into component integration testing and system integration testing.
What are the types of integration testing?
By approach: big bang, top-down, bottom-up and sandwich (hybrid). By scope: component integration and system integration testing.
What is third-party integration testing?
System integration testing against services you do not control, such as payment providers or external APIs. It checks your side handles their responses, errors and timeouts correctly.
Where does integration testing sit between unit and system testing?
After component (unit) testing has confirmed each part works alone, and before system testing checks the whole product end to end.
Need integration testing?
Tell us which systems talk to each other and where they have broken before. We will test those connections and keep testing them in your pipeline.