On 18 kesä, 12:23, Chris Wilson <[email protected]> wrote: > > I guess this should work by giving a message like this on test name > > clash: "ERROR: Multiple tests found: <list of test identifiers>". The > > user could then copy-paste the correct test and run the test by full > > identifier. > > I might deliberately want to run multiple tests in some cases. I was > thinking of adding wildcard search support too. It shouldn't be an error, > it should be explicitly supported.
It seems supporting both could achieved, for example using ".test_method" for exact match, if more than one match found then error and print identifiers, "test_method" searches runs all matches. The syntax is just an example, but it should be doable to have both. I do have a need to run just a single test, as that way it is easier to use pdb breakpoints. If there is an easy way to get a breakpoint which fires only when running test_method_x, I am all ears. > Fine by me. How about a contrib test runner? And does anyone have time to > write some tests for a test runner? Contrib isn't the right place for this. The idea is that if it is not in core or contrib then you can change the interface easily. Even if this feature is done in contrib, changes have to go through the deprecation cycle. There are no experimental features in Django, so we can't test the interface anywhere in core or contrib. Of course, if we can get a consensus on the correct interface here on django- developers, or from some existing test runner, then direct core could be possible. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
