#28790 closed Cleanup/optimization (fixed)
Document how to avoid running certain test classes in parallel
Reported by: | Tobias Krönke | Owned by: | Caio Ariede |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
In PR https://github.com/django/django/pull/9342 I propose to enable users to mark tests for non-parallel execution. In this way, they don't have to make sure, that all their tests are properly isolated. This is useful, if you work with other external storages like e.g. solr and django-haystack.
Change History (11)
comment:1 by , 7 years ago
Description: | modified (diff) |
---|
comment:2 by , 7 years ago
Description: | modified (diff) |
---|
comment:3 by , 7 years ago
comment:4 by , 7 years ago
I don't want to be too eager for this to be merged. I probably wouldn't have looked any further had I known this Mixin. Still I would like to point out some advantages of my solution:
- Less complex to use
- Less complex implementation (especially no lock files involved)
- More efficient, if you have only 1 shared resource (no concurrent waits for the locked file)
Of course I also see the advantage of the existing mixin, that you can use different lock files for different shared resources if you have many. A hint in the docs would be quite pleasant.
So, your call ;-)
comment:5 by , 7 years ago
Component: | Testing framework → Documentation |
---|---|
Has patch: | unset |
Summary: | Provide a mixin to run certain test classes not in parallel → Document how to avoid running certain test classes in parallel |
Triage Stage: | Unreviewed → Accepted |
Type: | New feature → Cleanup/optimization |
I guess it's better to document the existing class rather than add another one unless the new implementation is preferred for some reason.
comment:6 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:8 by , 5 years ago
Has patch: | set |
---|
Isn't this is already provided by ba813864870d63de1d1679271c38a3c15e94e934? It could probably be documented if needed.