#4460: runtests.py can't easily control which tests to run
--------------------------------------------------+-------------------------
Reporter: Brian Harring <[EMAIL PROTECTED]> | Owner:
adrian
Status: new | Component: Unit
test system
Version: SVN | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------------+-------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
Replying to [comment:2 Brian Harring <[EMAIL PROTECTED]>]:
> Replying to [comment:1 mtredinnick]:
> > Although the help string is a little misleading, you can already do
most of what you want here (bearing in mind that runtests is only for
testing django core code, not third-party apps).
> Don't have the same level of control though; try it for django.contrib
(if that's defined as third party apps, next question is "why does
runtests.py run those fixtures then?" :)
Let's try to avoid nit-picking. Core includes the contrib apps shipped
with core. We maintain those as well ...they are not third-party.
Your other comment comes back to wanting fine-grained control, which
doesn't require adding bits in ''front'' of the name. Adding bits behind
the name for sub-pieces would be most welcome.
>
> Counter example there is if there is a duplicate regressiontests and
modeltests submodule; right now y'all are dodging it via redundancy in the
naming (regressiontests/one_to_one_regress and modeltests/one_to_one,
regressiontests/many_to_one_regress and modeltests/many_to_one for
example).
By being a little careful up front, we save typing when running tests.
Good (and deliberate) trade-off right there -- a developer run tests far
more often than you create a new directory for tests.
> > What use case is missing? This might just need a documentation fix.
> Inability to run django.contrib.*, inability to run just submodules of a
specific test scenario- the selection atm in runtests.py is basically
limiting it to the second level module of {model,regression}tests- what if
you specifically need to (currently not possible, but run with it) test
modeltests.dispatch.tests.test_dispatcher ?
>
> What I'm after with this mod is getting closer to granularity possible
in other test runners- best case, ability to nail it down to running a
single test. Current form of runtests doesn't allow it, only allows
running (basically) classes of tests. This patch ought to get it to that
point.
Adding a dot notation for a particular named test below the existing
directory specification structure would be good.
Adding full paths when they aren't particularly needed is just asking us
to type an extra dozen or so characters without a convincingly good
reason.
--
Ticket URL: <http://code.djangoproject.com/ticket/4460#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
