Opened 9 years ago
Closed 9 years ago
#26448 closed Cleanup/optimization (fixed)
Improve docs for running tests using a different database
Reported by: | Anna Schneider | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.9 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description (last modified by )
For new contributors working on contrib.postgres
, it is confusing when the tests in postgres_tests
are skipped by default. Some possible improvements include:
In the "skipped tests" paragraph of https://docs.djangoproject.com/en/1.9/intro/contributing/#running-django-s-test-suite-for-the-first-time, mention that another reason that tests might get skipped is if the tests are specific to a non-sqlite database. Add a link to https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code/unit-tests/#using-another-settings-module to help people use a different settings module.
In https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code/unit-tests/#using-another-settings-module, clarify that the default settings module is located at django/tests/test_sqlite.py
.
Change History (5)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Easy pickings: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 9 years ago
comment:4 by , 9 years ago
Has patch: | set |
---|
Greetings,
aschn and timgraham, I just updated the documentation to reflect the suggestions and I have created a pull request for the same - https://github.com/django/django/pull/6418
Thank you.