Wednesday, October 21, 2015

Re: duplicated selenium test fails

Thanks Carl!

Am 21.10.2015 um 00:18 schrieb Carl Meyer:
> On 10/19/2015 03:03 AM, Ulrich Laube wrote:
>> It boils down to this:
>> [...]
>> Is it a known problem?
>
> Not really a problem - you just need to be aware that you can't rely on
> consistent database IDs in tests.

So there is no test isolation where I assumed it to be.
My assumption was, that each

class younameit(TestCase)

gets its own fresh database to work with, so that all

def test_foobar(self):

within, would work against the same DB.
Thanks for pointing that out to me.

Uli

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/56275302.1030909%40informatik.uni-kl.de.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment