mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-18 02:56:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Merge 41e73abe91 into 1ce6e78dd4

Browse source
This commit is contained in:
Youngkwang Yang 2025-11-18 01:17:16 +09:00 • committed by GitHub
commit 374f35d8b6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/ref/django-admin.txt
View file

@ -1488,6 +1488,22 @@ subsequent run. Unless the :setting:`MIGRATE <TEST_MIGRATE>` test setting is
``False``, any unapplied migrations will also be applied to the test database
before running the test suite.
.. warning::
When using ``--keepdb`` with :option:`test --parallel`, new migrations
are not automatically applied to clone databases (e.g., ``test_1``,
``test_2``).
While migrations are applied to the main test database, clones retain
their existing schema. This can cause test failures with errors such as
"column does not exist" or "relation does not exist" after adding
migrations.
To avoid this, either omit ``--keepdb`` when you have schema changes,
or manually delete the clone databases before running tests.
This is a known limitation. See :ticket:`26822` for details.
.. django-admin-option:: --shuffle [SEED]
Randomizes the order of tests before running them. This can help detect tests

3
docs/topics/testing/overview.txt
View file

@ -359,6 +359,9 @@ Running tests in parallel
As long as your tests are properly isolated, you can run them in parallel to
gain a speed up on multi-core hardware. See :option:`test --parallel`.
See :option:`test --keepdb` for a known limitation when combining these options
(:ticket:`26822`).
Password hashing
~~~~~~~~~~~~~~~~