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
A [`Makefile`](./Makefile) has been included in the project which should make it straightforward to start the project locally. We utilize virtual environments (see [`virtualenv`](https://docs.python.org/3/tutorial/venv.html)) in order to provide isolated development environments for the project. This reduces the risk of invalid or corrupt global packages. It also integrates nicely with Make, which will detect changes in the `requirements-dev.txt` file and update the virtual environment if any occur.
16
+
17
+
Run `make init` to initialize the project's virtual environment and install all dev dependencies.
18
+
19
+
### Testing
20
+
21
+
Run tests with `make test`.
22
+
23
+
We use `pytest` for our unit testing, making use of `parametrized` to inject cases at scale.
24
+
25
+
### Integration tests
26
+
27
+
These are planned once the SDK has been stabilized and a Flagd provider implemented. At that point, we will utilize the [gherkin integration tests](https://github.com/open-feature/test-harness/blob/main/features/evaluation.feature) to validate against a live, seeded Flagd instance.
28
+
29
+
### Packaging
30
+
31
+
We publish to the PyPI repository, where you can find this package at [openfeature-sdk](https://pypi.org/project/openfeature-sdk/).
32
+
33
+
## Pull Request
34
+
35
+
All contributions to the OpenFeature project are welcome via GitHub pull requests.
36
+
37
+
To create a new PR, you will need to first fork the GitHub repository and clone upstream.
0 commit comments