#28790: Document how to avoid running certain test classes in parallel
--------------------------------------+------------------------------------
Reporter: Tobias Krönke | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
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 Tim Graham):
* component: Testing framework => Documentation
* has_patch: 1 => 0
* type: New feature => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I guess it's better to document the existing class rather than add another
one unless the new implementation is preferred for some reason.
--
Ticket URL: <https://code.djangoproject.com/ticket/28790#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.4c20bb59b8de88244cf9f0e4edec60b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
