When testing code that makes use of third-party libraries, we can mock out the dependencies for fast but incomplete tests. Or we can do full integration tests which are slow and potentially flaky. These are our two options, right?
Well, maybe not. In today’s episode, guest chef Nathan Ladd makes a case for a third way: test substitutes that are maintained alongside a production API. He’ll show you an example of how to implement such a substitute, inspired by real-world experience. Enjoy!