I discovered that it gets not execute by looking at the coverage statistics.
But you're totally right. I had a second method that is called the same. Very embarrassing for me. Sorry. Gregor 2009/8/28 Karen Tracey <kmtra...@gmail.com>: > On Thu, Aug 27, 2009 at 2:21 PM, Gregor Müllegger <gre...@muellegger.de> > wrote: >> >> Hi, >> >> i have an issue with the standard test runner of django. If i try to >> run the testsuite of an app everything gets executed in the right >> fashion. While all executed tests pass without errors, the test method >> "test_string_regex" is not evaluated! If i rename the method to any >> athor name like "test_string_regex2", "test_string__regex" or >> "test__string_regex" it is discovered by the test suite. >> I also can execute the single test with the "python manage.py test >> applabel.TestCaseName.test_string_regex". >> >> This seams very scary to me. >> Is this a bug in the django testrunner? > > Unlikely. More likely there is something in your test suite causing this. > How are you determining that this method is not running when you run the > full suite? Are you sure you don't have multiple test_string_regex methods > defined in this TestCase? > > FWIW, I just tried adding a method with that name to a test suite I have and > it runs fine. > > Karen > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
