Don't Mock What You Don't Own

Trying to test code that interacts with third-party APIs has always been a controversial topic.

Shouldn't your tests be able to run without internet access?

If you're using a library that's already been tested, why not mock it out?

In this screencast (taken from my Test-Driven Laravel course), I walk through two possible approaches, and explain why I think it's worth the cost to integrate with external services in your adapter tests.

Trying to wrap your head around testing? Test-Driven Laravel is a course I recently launched that teaches you how to TDD an app from start to finish. Learn more about it here.