thanks for all the answers and your patience. got the basic testing-
setup now ...
patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
> self.assertEquals(list(self.movie.details_genre.all()), "[ Action-Komödie>, ]")
> ...
>
> output:
> AssertionError: [, ] !
> = '[, \xc3\xb6die>]'
First, it looks like you're comparing a list of objects to a string.
I'm not sure if QuerySets override the magic method to determine
if they're
thanks. that works.
now I´m getting an error due to some unicode related stuff:
...
self.assertEquals(list(self.movie.details_genre.all()), "[, ]")
...
output:
AssertionError: [, ] !
= '[, ]'
thanks,
patrick
On 13 Aug., 17:03, Tim Chase <[EMAIL PROTECTED]> wrote:
> > now, I just ran into a
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]>
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
On 13 Sie, 09:48, 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").
./manage.py test --verbosity 2
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").
in the django-docs it says, that doctests provide automatic
documentation. what exactly does
On 8/10/07, patrickk <[EMAIL PROTECTED]> wrote:
>
> here are a couple of questions:
> 1. where to define the testing? in models.py or in tests.py? I´d like
> to seperate the testing from models.py, so how can I write doctests
> in a seperate file (the example in the django documentation only
>
> if you have an app named "tests" and you add it to your INSTALLED_APPS
> (which I guess is necessary) - does django create any tables or any
> content (e.g., additional content-types) outside the test-database?
I would proffer that unless there's a pressing reason to name
your app "tests"
thanks tim. that´s very useful.
one additional question:
if you have an app named "tests" and you add it to your INSTALLED_APPS
(which I guess is necessary) - does django create any tables or any
content (e.g., additional content-types) outside the test-database?
patrick.
On Aug 10, 2:19 pm,
> 1. where to define the testing? in models.py or in tests.py? I´d like
> to seperate the testing from models.py, so how can I write doctests
> in a seperate file (the example in the django documentation only
> explains seperate unit-testing)?
my understanding is that doctests can only be
I´ve been reading the slides for "Django Master Class" and the django
documentation on testing, but I´m still not sure how to actually do
some testing.
here are a couple of questions:
1. where to define the testing? in models.py or in tests.py? I´d like
to seperate the testing from
12 matches
Mail list logo
