#33264: DiscoverRunner doesn't counts unexpectedSuccess as an error
-----------------------------------+------------------------------------
Reporter: Baptiste Mispelon | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 3.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Changes (by Mariusz Felisiak):
* stage: Unreviewed => Accepted
Comment:
Thanks for the report! As far as I'm aware this doesn't qualify for a
backport and yes it's backward incompatible. This behavior is in Django
from the very beginning (e.g. we take errors into account from 2007, see
c1a73d80da65694319d803160b5e400e11318213). Python's `TestResult` treats
unexpected successes as a tests failure since version
[https://docs.python.org/3/library/unittest.html?highlight=unexpectedsuccesses#unittest.TestResult.wasSuccessful
3.4].
I'd change this in Django 4.1 without a deprecation period.
--
Ticket URL: <https://code.djangoproject.com/ticket/33264#comment:1>
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/067.f3f27a219ea9f447665df82ac13dc4e5%40djangoproject.com.
