Testing Microservices

Microservices make testing harder because services are owned, deployed, and changed independently.

A change in one service can break another, but testing the full system every time is slow, costly, and often flaky.

Good microservices testing builds confidence without running every service for every test. It relies on fast unit tests, contract tests for service boundaries, focused integration tests, and a small number of end-to-end tests.

This chapter covers the microservices test pyramid, contract testing, chaos engineering, test data, and synthetic production tests.