Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #31 +/- ##
==========================================
+ Coverage 91.44% 91.65% +0.20%
==========================================
Files 7 7
Lines 526 539 +13
==========================================
+ Hits 481 494 +13
Misses 45 45
☔ View full report in Codecov by Sentry. |
|
@mikemhenry is probably going to be the CI wizard here getting postgres hooked up @dwhswenson rather than toggling between sqlite/other backends, could instead the fixture just look for a |
|
If this is working then I am not sure if you need me to do anything, but this is how I did this in the past: https://github.com/samplchallenges/SAMPL-league/blob/main/.github/workflows/CI.yml#L23-L38 Then just used the standard stuff with pytest/django testing but I think what David has setup makes it easier to run tests locally if you don't want to use your system's postgress or run a container locally |
This works locally, although it may take some work to get it running in the CI workflow.
EXORCIST_TEST_DB;sqlite(default) orpostgresfresh_db(which is most of them) will switch database backend. Obviously, tests offrom_filenameare still using SQLite even if you request postgres.installandcreatestages because create is more likely to be reused again locally thaninstall(e.g., delete the directory that contains the DB)restartandstopmainly so I don't have to look up thepg_ctldocumentation (since I probably won't even remember that the command is calledpg_ctl).