Join us and get access to thousands of tutorials and a community of expert Pythonistas.
This lesson is for members only. Join us and get access to thousands of tutorials and a community of expert Pythonistas.
What Is patch()?
00:00
So far throughout this course, we’ve been doing things like mocking entire modules within the same file as our tests. So for example, here’s my_calendar and I cleaned it up a little bit.
00:13
I removed all the tests and just have the core functions is_weekday() and get_holidays(). We’ve been things like requests is a Mock object and setting the side effects of requests.get()—
00:30 this is okay for very simple use cases and experimenting, but usually you would want to patch objects in separate files. Having your tests in a separate file is good for organization, it’s a good practice to do that, and you want to separate your mock objects from your actual codebase, right?
00:53
So, this is our codebase. This is our my_calendar module. We don’t really want to have Mock objects in here—we want to have them in our tests file.
01:03
So what I’ve done is I created another file called tests.py. It is located in the same directory as my_calendar.py and that’s going to be important because we’re going to be doing some importing.
01:15
What we’ll learn about next is the patch() method. The patch() method is really useful for importing Mock objects into your tests—importing functionality from your codebase into your tests.
Become a Member to join the conversation.