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:32:25 +0200 |
| commit | 7d8d2b56be12fd573dccba41cbeebfa2cea61534 (patch) | |
| tree | f4b65e0002751b4fbd8e5b2462344a66454d50e5 /docs/ref/django-admin.txt | |
| parent | 7c70aa8f6376d761bd6d4bc075d232ee6e91f8f2 (diff) | |
[3.0.x] Fixed #28790 -- Doc'd how to avoid running certain test classes in parallel.
Backport of dafdfd6a60638c4edcca7c4e65d11c0af654d759 from master
Diffstat (limited to 'docs/ref/django-admin.txt')
| -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 1f76879c23..e665cebf8b 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -1418,6 +1418,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: |