André Schaffer from Spotify Labs published article about Spotify’s journey to microservices testing. In a microservices world achieving confidence that the code does what it should, provide feedback that is fast and with easy maintenance became an art.
For a long time testing pyramid was an extremely efficient way to organize tests. In a microservices world, this is no longer the case, and we would argue that it can be actively harmful.
The biggest complexity in a microservice is not within the service itself, but in how it interacts with others, and that deserves special attention.
Author suggests that a more fitting way of structuring our tests for microservices would be the testing honeycomb. And what we should aim for instead is integration tests, which verify the correctness of our service in a more isolated fashion while focusing on the interaction points and making them very explicit. Interesting read!
[Read More]