feat: run automated workflow for CI tests#5
Conversation
| with: | ||
| python-version: "3.10" | ||
|
|
||
| - run: pip install -e ".[dev]" |
There was a problem hiding this comment.
it seems this is a uv project, why are we using pip here?
There was a problem hiding this comment.
We're not requiring uv for dhis2eo, trying to keep it light and use builtin tooling as much as possible, and dependencies aren't so big that we need the speed of uv.
| Until we make the first Github release, just install from the main Github repo: | ||
|
|
||
| ```bash | ||
| pip install git+https://github.com/dhis2/dhis2eo |
There was a problem hiding this comment.
should we also include uv instructions?
There was a problem hiding this comment.
I think we could have a PR later that maybe adds more support and instructions for uv users
| To avoid unnecessary computation and server load, tests for the `data` integrations are marked with `@pytest.mark.integration` and are skipped by default. To run them manually: | ||
|
|
||
| ```bash | ||
| pytest -v -m integration |
There was a problem hiding this comment.
This is better done with a Makefile
There was a problem hiding this comment.
The approach to dhis2eo is to keep it lightweight with fewer extra installs, not everyone is used to Makefiles and would need to be installed on Windows.
2 participants
https://dhis2.atlassian.net/browse/CLIM-358
pytest -v -m integration