From ce130749d51302006f76e33b9987eaec20589837 Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Thu, 29 Apr 2021 23:25:34 +0430 Subject: [PATCH] [3.2.x] Refs #32178 -- Doc'd DatabaseFeatures.django_test_skips/django_test_expected_failures in contributing guide. Backport of ca34db46504fca1221e27f6ab13734dfdfde6e1c from main --- docs/internals/contributing/writing-code/unit-tests.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 21a0d3d003..fc87c6540f 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -153,7 +153,10 @@ The included settings module (``tests/test_sqlite.py``) allows you to run the test suite using SQLite. If you want to run the tests using a different database, you'll need to define your own settings file. Some tests, such as those for ``contrib.postgres``, are specific to a particular database backend -and will be skipped if run with a different backend. +and will be skipped if run with a different backend. Some tests are skipped or +expected failures on a particular database backend (see +``DatabaseFeatures.django_test_skips`` and +``DatabaseFeatures.django_test_expected_failures`` on each backend). To run the tests with different settings, ensure that the module is on your :envvar:`PYTHONPATH` and pass the module with ``--settings``.