#25735 closed New feature (fixed)
Add test tagging to Django test runner
Reported by: | Carl Meyer | Owned by: | Jakub Paczkowski |
---|---|---|---|
Component: | Testing framework | Version: | 1.8 |
Severity: | Normal | Keywords: | |
Cc: | jakub@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
This idea has come up multiple times in the last few years, most recently in the discussion of #25653.
A pull request for it already exists: https://github.com/django/django/pull/5585
Change History (10)
comment:1 by , 9 years ago
Triage Stage: | Ready for checkin → Accepted |
---|
comment:2 by , 9 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
I think we should go ahead with this as-is, and if it turns out in practice skipping would be better, that can be done as a follow-up improvement.
comment:3 by , 9 years ago
Cc: | added |
---|---|
Owner: | changed from | to
Status: | new → assigned |
And PR is here: https://github.com/django/django/pull/5585
comment:4 by , 9 years ago
Patch needs improvement: | set |
---|---|
Triage Stage: | Ready for checkin → Accepted |
Left comments for improvement.
Note:
See TracTickets
for help on using tickets.
There is perhaps one other design decision we should at least consider before this is merged. The current implementation filters out tests that are de-selected by tags from the test suite, so it will be as if those tests weren't discovered at all. Is that what we want, or would it be better if de-selected tags were skipped using the unittest test-skipping functionality?
I haven't investigated feasibility of the latter, but I think it should be possible if we prefer it.