#25889: Organize tests in tests/queries
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: reficul31
Type: | Status: assigned
Cleanup/optimization |
Component: Testing framework | 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
-------------------------------------+-------------------------------------
Comment (by reficul31):
Replying to [comment:1 Tim Graham]:
> If we can break up the single `tests.py` file into multiple tests files
(perhaps based on the models they use) and `models.py` into a package
similar to `tests/auth_tests/models`, I think that would be a useful task.
If we can do some renaming along the way, that seems okay but it would be
easiest to review in a separate commit from one that moves things around.
I think this sort of thing won't be easy. As most of the models aren't
reused. If the patch required something there was a high chance that the
contributor made the model similar to that given in the ticket. According
to me the maximum we can do is to rename the tests such that they provide
the context of what the test is for without loosing the information
provided by the original author of the test.
--
Ticket URL: <https://code.djangoproject.com/ticket/25889#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/065.b7e79eca3b8f7889d5bae14eaf820014%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
