Skip to content

Commit 21abfb9

Browse files
adchiagitbook-bot
authored andcommitted
GitBook: [master] one page modified
1 parent ea9693b commit 21abfb9

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/how-to-guides/adding-or-reusing-tests.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,15 @@
11
# Adding or reusing tests
22

3+
## Overview
4+
35
This guide will go over
46

57
1. how Feast tests are setup
68
2. how to extend the test suite to test new functionality
79
3. how to use the existing test suite to test a new custom offline / online store.
810

11+
## Test suite overview
12+
913
Let's inspect the test setup as is:
1014

1115
```bash
@@ -53,6 +57,8 @@ $ tree
5357

5458
`feature_repos` has setup files for most tests in the test suite and sets up pytest fixtures for other tests. Crucially, this parametrizes on different offline stores, different online stores, etc and abstracts away store specific implementations so tests don't need to rewrite e.g. uploading dataframes to a specific store for setup.
5559

60+
## Understanding an example test
61+
5662
Let's look at a sample test using the universal repo:
5763

5864
{% tabs %}
@@ -140,6 +146,8 @@ def test_historical_features(environment, universal_data_sources, full_feature_n
140146

141147
The key fixtures are the `environment` and `universal_data_sources` fixtures, which are defined in the `feature_repos` directories. This by default pulls in a standard dataset with driver and customer entities, certain feature views, and feature values. By including the environment as a parameter, the test automatically parametrizes across other offline / online store combinations.
142148

149+
## Writing a new test or reusing existing tests
150+
143151
To:
144152

145153
* Include a new offline store:

0 commit comments

Comments
 (0)