mirror of
https://github.com/django/django.git
synced 2025-01-03 06:55:47 +00:00
Replaced "Django test runner" with DiscoverRunner in release notes.
Removed mention of options supported only by runtests.py.
This commit is contained in:
parent
02a600ff67
commit
d70b79c6b9
@ -362,14 +362,8 @@ Tests
|
|||||||
references, and entity references that refer to the same character as
|
references, and entity references that refer to the same character as
|
||||||
equivalent.
|
equivalent.
|
||||||
|
|
||||||
* Django test runner now supports headless mode for selenium tests on supported
|
* :class:`~django.test.runner.DiscoverRunner` can now spawn a debugger at each
|
||||||
browsers. Add the ``--headless`` option to enable this mode.
|
error or failure using the :option:`test --pdb` option.
|
||||||
|
|
||||||
* Django test runner now supports ``--start-at`` and ``--start-after`` options
|
|
||||||
to run tests starting from a specific top-level module.
|
|
||||||
|
|
||||||
* Django test runner now supports a ``--pdb`` option to spawn a debugger at
|
|
||||||
each error or failure.
|
|
||||||
|
|
||||||
.. _backwards-incompatible-3.0:
|
.. _backwards-incompatible-3.0:
|
||||||
|
|
||||||
|
@ -475,8 +475,8 @@ Tests
|
|||||||
* The new :setting:`MIGRATE <TEST_MIGRATE>` test database setting allows
|
* The new :setting:`MIGRATE <TEST_MIGRATE>` test database setting allows
|
||||||
disabling of migrations during a test database creation.
|
disabling of migrations during a test database creation.
|
||||||
|
|
||||||
* Django test runner now supports a :option:`test --buffer` option to discard
|
* :class:`~django.test.runner.DiscoverRunner` can now discard output for
|
||||||
output for passing tests.
|
passing tests using the :option:`test --buffer` option.
|
||||||
|
|
||||||
* :class:`~django.test.runner.DiscoverRunner` now skips running the system
|
* :class:`~django.test.runner.DiscoverRunner` now skips running the system
|
||||||
checks on databases not :ref:`referenced by tests<testing-multi-db>`.
|
checks on databases not :ref:`referenced by tests<testing-multi-db>`.
|
||||||
|
@ -367,8 +367,7 @@ Tests
|
|||||||
serialized to allow usage of the
|
serialized to allow usage of the
|
||||||
:ref:`serialized_rollback <test-case-serialized-rollback>` feature.
|
:ref:`serialized_rollback <test-case-serialized-rollback>` feature.
|
||||||
|
|
||||||
* Django test runner now supports a :option:`--buffer <test --buffer>` option
|
* The :option:`test --buffer` option now supports parallel tests.
|
||||||
with parallel tests.
|
|
||||||
|
|
||||||
* The new ``logger`` argument to :class:`~django.test.runner.DiscoverRunner`
|
* The new ``logger`` argument to :class:`~django.test.runner.DiscoverRunner`
|
||||||
allows a Python :py:ref:`logger <logger>` to be used for logging.
|
allows a Python :py:ref:`logger <logger>` to be used for logging.
|
||||||
@ -376,8 +375,8 @@ Tests
|
|||||||
* The new :meth:`.DiscoverRunner.log` method provides a way to log messages
|
* The new :meth:`.DiscoverRunner.log` method provides a way to log messages
|
||||||
that uses the ``DiscoverRunner.logger``, or prints to the console if not set.
|
that uses the ``DiscoverRunner.logger``, or prints to the console if not set.
|
||||||
|
|
||||||
* Django test runner now supports a :option:`--shuffle <test --shuffle>` option
|
* :class:`~django.test.runner.DiscoverRunner` can now execute tests in a random
|
||||||
to execute tests in a random order.
|
order using the :option:`test --shuffle` option.
|
||||||
|
|
||||||
* The :option:`test --parallel` option now supports the value ``auto`` to run
|
* The :option:`test --parallel` option now supports the value ``auto`` to run
|
||||||
one test process for each processor core.
|
one test process for each processor core.
|
||||||
|
@ -534,8 +534,9 @@ Miscellaneous
|
|||||||
on the :class:`~django.db.models.Model` instance to which they belong. *This
|
on the :class:`~django.db.models.Model` instance to which they belong. *This
|
||||||
change was reverted in Django 4.1.2.*
|
change was reverted in Django 4.1.2.*
|
||||||
|
|
||||||
* The Django test runner now returns a non-zero error code for unexpected
|
* :class:`~django.test.runner.DiscoverRunner` now returns a non-zero error code
|
||||||
successes from tests marked with :py:func:`unittest.expectedFailure`.
|
for unexpected successes from tests marked with
|
||||||
|
:py:func:`unittest.expectedFailure`.
|
||||||
|
|
||||||
* :class:`~django.middleware.csrf.CsrfViewMiddleware` no longer masks the CSRF
|
* :class:`~django.middleware.csrf.CsrfViewMiddleware` no longer masks the CSRF
|
||||||
cookie like it does the CSRF token in the DOM.
|
cookie like it does the CSRF token in the DOM.
|
||||||
|
@ -432,8 +432,9 @@ Tests
|
|||||||
|
|
||||||
* :class:`~django.test.AsyncClient` now supports the ``follow`` parameter.
|
* :class:`~django.test.AsyncClient` now supports the ``follow`` parameter.
|
||||||
|
|
||||||
* The new :option:`test --durations` option allows showing the duration of the
|
* :class:`~django.test.runner.DiscoverRunner` now allows showing the duration
|
||||||
slowest tests on Python 3.12+.
|
of the slowest tests using the :option:`test --durations` option (available
|
||||||
|
on Python 3.12+).
|
||||||
|
|
||||||
Validators
|
Validators
|
||||||
~~~~~~~~~~
|
~~~~~~~~~~
|
||||||
|
@ -280,9 +280,6 @@ Tests
|
|||||||
:meth:`~django.test.SimpleTestCase.assertInHTML` assertions now add haystacks
|
:meth:`~django.test.SimpleTestCase.assertInHTML` assertions now add haystacks
|
||||||
to assertion error messages.
|
to assertion error messages.
|
||||||
|
|
||||||
* The Django test runner now supports a ``--screenshots`` option to save
|
|
||||||
screenshots for Selenium tests.
|
|
||||||
|
|
||||||
* The :class:`~django.test.RequestFactory`,
|
* The :class:`~django.test.RequestFactory`,
|
||||||
:class:`~django.test.AsyncRequestFactory`, :class:`~django.test.Client`, and
|
:class:`~django.test.AsyncRequestFactory`, :class:`~django.test.Client`, and
|
||||||
:class:`~django.test.AsyncClient` classes now support the ``query_params``
|
:class:`~django.test.AsyncClient` classes now support the ``query_params``
|
||||||
|
Loading…
Reference in New Issue
Block a user