using doctests works fine so far. now, I just ran into a problem with unittests:
... self.assertEquals(self.movie.details_country.all(), []) ... the output is: AssertionError: [] != [] isn´t that supposed to work? thanks, patrick On 13 Aug., 13:14, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 8/13/07, patrickk <[EMAIL PROTECTED]> wrote: > > > > > thanks russ. > > > is it possible to make the testing-output more verbose? I tried "-v", > > but that doesn´t work. It´d be nice to see what tests have been > > running and what the output is (more than just "OK"). > > --verbosity=[0|1|2]. It's in the help when you run ./manage.py. > > > in the django-docs it says, that doctests provide automatic > > documentation. what exactly does that mean? does it refer to the tests > > written within the model or is it possible to generate some output > > (html-file)? > > > concerning the django-docs: > > from my point of view, the description of where to define the tests is > > not easy to understand. > > e.g., it says "You can put doctest strings on any object in your > > models.py, but it's common practice to put application-level doctests > > in the module docstring, and model-level doctests in the docstring for > > each model." > > whats the "module docstring"? > > Erm... the docstring for the module: > > http://www.python.org/dev/peps/pep-0257/ > > We need to walk a fine line here. If Python's documentation was poor, > there would be a good argument to be made here, but Python has > extensive documentation on the doctest and unittest modules. There > really isn't anything served by us duplicating Python's documentation > - in fact, it could be considered detrimental, because it suggests > that Django's test framework is somehow different to Python's. > > > one more issue: > > with our server-setup, it´s much easier to define a seperate user for > > the test-database (instead of using the user from the production- > > database). is that possible? > > Not at present. The test framework uses the main database login to get > access so it can create the test database; moving this into a separate > user could pose some interesting difficulties. I'm also hesitant to > start duplicating all the DB related settings to handle a test login. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
