#33213: Document coverage setup for parallel tests
-------------------------------------+-------------------------------------
Reporter: Mr. Glass | Owner: Paolo
| Melchiorre
Type: New feature | Status: closed
Component: Documentation | Version:
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"78da5ca0c1f2ab3201f8f6cd629e80d805ea023d" 78da5ca]:
{{{
#!CommitTicketReference repository=""
revision="78da5ca0c1f2ab3201f8f6cd629e80d805ea023d"
Reverted "Fixed #33213 -- Doc'd testing code coverage in parallel and used
it."
This reverts commit 69352d85fa8412865db9e0c7f177b333c0eac3e2.
Test coverage for async methods was no longer calculated with this
change.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33213#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186e52a37a4-1b7cd6d0-9c6e-42f9-b042-7ab9d9313336-000000%40eu-central-1.amazonses.com.
