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 Anna Schneider)

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 Anna Schneider, 9 years ago

Description: modified (diff)

comment:2 by Tim Graham, 9 years ago

Easy pickings: set
Triage Stage: UnreviewedAccepted

comment:3 by krisys, 9 years ago

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.

comment:4 by Tim Graham, 9 years ago

Has patch: set

comment:5 by Tim Graham <timograham@…>, 9 years ago

Resolution: fixed
Status: newclosed

In 361cb7a:

Fixed #26448 -- Added details for running tests with a different database backend.

Note: See TracTickets for help on using tickets.
Back to Top