You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,6 +93,10 @@ EASYPOST_TEST_API_KEY=123... EASYPOST_PROD_API_KEY=123... make coverage
93
93
94
94
# Run security analysis
95
95
make scan
96
+
97
+
# Update submodules
98
+
git submodule init
99
+
git submodule update --remote
96
100
```
97
101
98
102
### Testing
@@ -112,9 +116,8 @@ The following are required on every test run:
112
116
-`EASYPOST_TEST_API_KEY`
113
117
-`EASYPOST_PROD_API_KEY`
114
118
115
-
The following are required when you need to re-record cassettes for applicable tests (fallback values are used otherwise):
119
+
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:
116
120
117
121
-`USPS_CARRIER_ACCOUNT_ID` (eg: one-call buying a shipment for non-EasyPost employees)
122
+
-`PARTNER_USER_PROD_API_KEY` (eg: creating a referral user)
118
123
-`REFERRAL_USER_PROD_API_KEY` (eg: adding a credit card to a referral user)
119
-
120
-
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.
0 commit comments