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`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> For new contributors working on `contrib.postgres`, it is confusing when
> the tests in `test_postgres` 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`.
New description:
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`.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/26448#comment:1>
* easy: 0 => 1
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/26448#comment:2>
Comment (by krisys):
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/26448#comment:3>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/26448#comment:4>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"361cb7a857f1ca69754c0e3a0038097d09508f2c" 361cb7a]:
{{{
#!CommitTicketReference repository=""
revision="361cb7a857f1ca69754c0e3a0038097d09508f2c"
Fixed #26448 -- Added details for running tests with a different database
backend.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26448#comment:5>