#35849: ParallelTestSuite reports error occurred in arbitrary test instead of
setUpClass
--------------------------------------+------------------------------------
Reporter: David Winiecki | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: dev
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
--------------------------------------+------------------------------------
Comment (by Jacob Walls):
It makes sense to me to clean up the discrepancy between `parallel=1` and
`parallel=n`, if we can do it easily enough. The single process runner
uses `TextTestRunner`, but the parallel one does not, so it makes sense
that it's "on us" to mimic what `TextTestRunner` does to get consistent
test labels in this edge case. We might want to ensure ''unexpected
success'' is covered just like test errors.
> My impression is that I shouldn't create a PR to upstream until the
proposed git branch is almost ready to merge, but maybe that's not true.
Appreciate you being careful, but I think it's totally appropriate to open
a PR against upstream once the ticket's been accepted.
--
Ticket URL: <https://code.djangoproject.com/ticket/35849#comment:9>
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/01070192a2e0ebd8-8c0bbc8d-fa1e-43d7-ace9-6a60aab7ed74-000000%40eu-central-1.amazonses.com.
