feat: use new fixtures for tests

Author: Justintime50

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "examples"]
+	path = examples
+	url = https://github.com/EasyPost/examples

Makefile

@@ -41,10 +41,14 @@ install: | venv install-dev
 ## install-dev - Install dev requirements
 install-dev: | venv
 	$(VIRTUAL_BIN)/pip install -e ."[dev]"
+	git submodule init
+	git submodule update
 
 ## install-pypy - Install dev requirements for pypy
 install-pypy: | venv
 	$(VIRTUAL_BIN)/pip install -e ."[pypy_dev]"
+	git submodule init
+	git submodule update
 
 ## isort - Sorts imports throughout the project
 isort:

README.md

@@ -85,6 +85,10 @@ EASYPOST_TEST_API_KEY=123... EASYPOST_PROD_API_KEY=123... make coverage
 
 # Run security analysis
 make scan
+
+# Update submodules
+git submodule init
+git submodule update --remote
 ```
 
 ### Testing
@@ -104,9 +108,8 @@ The following are required on every test run:
 - `EASYPOST_TEST_API_KEY`
 - `EASYPOST_PROD_API_KEY`
 
-The following are required when you need to re-record cassettes for applicable tests (fallback values are used otherwise):
+Some tests may require an EasyPost user with a particular set of enabled features such as a `Partner` user when creating referrals. We have attempted to call out these functions in their respective docstrings. The following are required when you need to re-record cassettes for applicable tests:
 
 - `USPS_CARRIER_ACCOUNT_ID` (eg: one-call buying a shipment for non-EasyPost employees)
+- `PARTNER_USER_PROD_API_KEY` (eg: creating a referral user)
 - `REFERRAL_USER_PROD_API_KEY` (eg: adding a credit card to a referral user)
-
-Some tests may require a user with a particular set of enabled features such as a `Partner` user when creating referrals. We have attempted to call out these functions in their respective docstrings.