Skip to content

docs: Fix command to run python tests on documentation #4111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
franciscojavierarceo merged 1 commit into from
Apr 17, 2024
Merged

docs: Fix command to run python tests on documentation #4111

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/how-to-guides/customizing-feast/adding-a-new-offline-store.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs/how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down