integration test

A test that checks several real parts working together, such as the service talking to a real database.

In more detail

It catches routing, serialization and wiring mistakes that unit tests replace or mock away, at the cost of running more slowly. Integration tests usually cross a network or database boundary, so they need deterministic data and a real or realistic dependency.

Examples

In the APIs course: The course contract suite is an integration test: it starts the real server, sends real HTTP, reads headers and bodies, and uses the seeded database.
Integration tests check a boundary between components, such as a database or another service. An integration failure often points to a contract or environment problem.
The capstone suite routes simulated traffic through ingress, auth, the database and the outbox.
Java: Testcontainers starts a disposable PostgreSQL container for repository tests.
In this course: Integration tests verify the join between your code and a real dependency, which test doubles cannot: whether a SQL query is valid, a serializer matches the server, or a timeout is wired correctly. They are slower than unit tests, so keep them focused on boundaries where the real behaviour matters, and make setup, readiness and cleanup visible.

Related terms

Taught in

References

Certification courses