diff --git a/docs/how-to-guides/customizing-feast/adding-a-new-offline-store.md b/docs/how-to-guides/customizing-feast/adding-a-new-offline-store.md
index b2818b748f..9c4ed1c45a 100644
--- a/docs/how-to-guides/customizing-feast/adding-a-new-offline-store.md
+++ b/docs/how-to-guides/customizing-feast/adding-a-new-offline-store.md
@@ -381,7 +381,7 @@ Even if you have created the `OfflineStore` class in a separate repo, you can st
 2.  Make sure that your offline store doesn't break any unit tests first by running:
 
     ```
-    make test-python
+    make test-python-unit
     ```
 3.  Next, set up your offline store to run the universal integration tests. These are integration tests specifically intended to test offline and online stores against Feast API functionality, to ensure that the Feast APIs works with your offline store.
 
diff --git a/docs/how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md b/docs/how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md
index ab88ebaa20..e3f1fcf428 100644
--- a/docs/how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md
+++ b/docs/how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md
@@ -319,7 +319,7 @@ Even if you have created the `OnlineStore` class in a separate repo, you can sti
 1.  In the Feast submodule, we can run all the unit tests and make sure they pass:
 
     ```
-    make test-python
+    make test-python-unit
     ```
 2. The universal tests, which are integration tests specifically intended to test offline and online stores, should be run against Feast to ensure that the Feast APIs works with your online store.
    * Feast parametrizes integration tests using the `FULL_REPO_CONFIGS` variable defined in `sdk/python/tests/integration/feature_repos/repo_configuration.py` which stores different online store classes for testing.