TechPrufer
Get started
Spotify
Spotify logoSpotify · Feature trail

Microservices Testing Strategy

1 post · Dec 2017

What this trail covers

Spotify's approach to testing microservices has evolved from a traditional testing pyramid to a 'Testing Honeycomb' model. This new strategy emphasizes integration tests, with fewer implementation detail tests and ideally no integrated tests. The goal is to provide confidence, fast feedback, and easier maintenance by focusing on testing services at their interaction points and contracts, treating each microservice as a testable component.

All Spotify trails
  1. Testing of MicroservicesThis post introduces the 'Testing Honeycomb' model as a more suitable strategy for testing microservices compared to the traditional testing pyramid. It defines integrated tests as tests that depend on the correctness of other systems and advocates for minimizing them. Instead, it promotes integration tests that verify a service's correctness in isolation while explicitly testing interaction points. The post provides examples of how this strategy is applied to simple and complex microservices at Spotify, highlighting the trade-offs of slightly slower test execution for improved coding speed and maintainability. It also discusses the appropriate use of implementation detail tests for complex, isolated code segments.