diff options
| author | Caio Ariede <caio.ariede@gmail.com> | 2019-06-05 11:35:36 -0300 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-10-08 12:11:06 +0200 |
| commit | dafdfd6a60638c4edcca7c4e65d11c0af654d759 (patch) | |
| tree | 6d7b9388c88a001524486383bf4a9938e01ad2e8 /docs/ref | |
| parent | a28d1b38e55cf588cfaae97de6a575d5c9f90a96 (diff) | |
Fixed #28790 -- Doc'd how to avoid running certain test classes in parallel.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/django-admin.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index ea935501c6..f602e327cf 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -1402,6 +1402,12 @@ Each process gets its own database. You must ensure that different test cases don't access the same resources. For instance, test cases that touch the filesystem should create a temporary directory for their own use. +.. note:: + + If you have test classes that cannot be run in parallel, you can use + ``SerializeMixin`` to run them sequentially. See :ref:`Enforce running test + classes sequentially <topics-testing-enforce-run-sequentially>`. + This option requires the third-party ``tblib`` package to display tracebacks correctly: |