-
-
Notifications
You must be signed in to change notification settings - Fork 366
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.
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
Allow running tests using sqlite #516
Conversation
Codecov Report
@@ Coverage Diff @@
## master #516 +/- ##
=======================================
Coverage 95.15% 95.15%
=======================================
Files 6 6
Lines 825 825
=======================================
Hits 785 785
Misses 40 40 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
tests/settings.py
Outdated
else: | ||
DATABASES = { | ||
"default": { | ||
"ENGINE": "django.db.backends.postgresql_psycopg2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"django.db.backends.postgresql_psycopg2", should be just postgresql as per new django releases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, that will work dj2.2+ ; will update..
ping @auvipy. I can merge but would be bad practise IMO. |
Problem
Distro build workers do not want to install postgres in order to run the tests.
Solution
Added capability to use sqlite instead using env flag
SQLITE
Commandments
CHANGES.rst
file to describe the changes, and quote according issue withGH-<issue_number>
.