#32591: Change DiscoverRunner always to run _FailedTest "tests" first
-------------------------------------+-------------------------------------
Reporter: Chris | Owner: nobody
Jerdonek |
Type: | Status: new
Cleanup/optimization |
Component: Testing | Version: dev
framework | Keywords:
Severity: Normal | DiscoverRunner,_FailedTest
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Currently, `DiscoverRunner`'s default test order is to run `_FailedTest`
objects in a last "catch-all" test-type group, and to order them in no
particular way within that last group. Since Django already knows those
tests have failed, it seems like it would be better for the user if Django
always ran / reported those failed tests first. That would give the user
quicker feedback. Also, when `--failfast` is used, it would result in
tests failing faster (namely right away), instead of possibly waiting for
many tests to complete before getting to the `_FailedTest`.
This could be implemented by changing
[https://github.com/django/django/blob/f5a22442176878d07e80ae5ba0af1dd8d6910fbd/django/test/runner.py#L813
reorder_tests()] to prepend its list of classes with a bin for
`_FailedTest` objects.
--
Ticket URL: <https://code.djangoproject.com/ticket/32591>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.718dbaf10e3f20a192c7c53e20fdf94c%40djangoproject.com.
