On 14/06/12 11:51, Anssi Kääriäinen wrote: > On 14 kesä, 13:35, Chris Wilson <ch...@aptivate.org> wrote: >> I've made some improvements (in my view) to the DjangoTestSuiteRunner. I >> got tired of having to remember my test class names and of typing so much: >> >> ./manage.py test binder.BinderTest.test_can_create_users >> >> This new version searches for tests with the given name in all >> INSTALLED_APPS, so you can just type this: >> >> ./manage.py test test_can_create_users > > A big +1 to easier running of single tests. I haven't checked the > implementation / API details at all. But I do know I would have > immediate use for this feature in running Django's tests.
+1 from me as well - the test runner you linked to looks reasonably sane, only a few small things that I'm questioning (like why types is imported inside the for loop). > Another feature which I would find useful would be "--log-failed- > cases=somefile". Then you could re-run the failed tests using: > > ./manage.py test < somefile > > I would find this very useful in fixing regressions - run the full > test suite - fix regressions - try to run the failed cases - fix more > - run the failed cases again - when done rerun full test suite. > > Anybody else for this feature? Interesting idea - I can see that being useful, too. Presumably we're just talking an output with one test function reference per line? Not sure about having to read from stdin - I can see that potentially interfering with things like pdb.set_trace() - but there's always the option of adding a command-line flag too. Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
