Hands-On Microservices with Kubernetes

Should you test everything?

The answer is no! Testing provides a lot of value, but has costs too. The marginal value of adding tests is decreasing. Testing everything is difficult, if not impossible. Considering that testing takes time to develop, it can slow down changes to the system (you need to update the tests), and the tests might need to change when dependencies change. Testing also takes time and resources to run, which can slow down the edit-test-deploy cycle. Also, tests can have bugs too. Finding the sweet spot of how much testing you need is a judgement call.

Unit tests are very valuable, but they are not enough. This is especially true for microservice-based architectures where there are a lot of small components that may work ...