In this chapter, we covered the topic of testing and its various flavors: unit testing, integration testing, and all kinds of end-to-end testing. We also dived deep into how Delinkcious tests are structured. We explored the link manager unit tests, added a new smoke test, and introduced Telepresence for expediting the edit-test-debug life cycle against a real Kubernetes cluster while modifying the code locally.
That being said, testing is a spectrum that has costs, and just blindly adding more and more tests doesn't make your system better or higher quality. There are many important trade-offs between quantity and quality of tests, such as the time it takes to develop and maintain the tests, the time and resources it takes to run the tests, and the number and complexity of problems that tests detect early. You should have enough context to make those tough decisions...