Re: Unittest test-database not empty

2008-03-29 Thread Emil Stenström
Hi rock, I had the same problem and traced it to one of the contrib.auth tests. It seems they don't delete two of the testusers there. I added a ticket about it (http://code.djangoproject.com/ticket/6923), and will just use another username for my own tests meanwhile. /Emil On 30 Jan, 10:34,

Re: Unittest test-database not empty

2008-01-30 Thread rock
I have no fixtures/initial_data-files anywhere in my project tree! Actually, the only file named "initial_data" on my system is djtrunk/ tests/modeltests/fixtures/fixtures/initial_data.json. And that file doesn't contain much. The "ghost-users" only show up when I'm running "./manage.py test".

Re: Unittest test-database not empty

2008-01-29 Thread Russell Keith-Magee
On Jan 30, 2008 5:36 AM, rock <[EMAIL PROTECTED]> wrote: > > Thanks Russ, for your helpful comments! > > I'm now searching for the initial_data fixture. I have looked through > all files in this project without success. When I run > > python manage.py test > > there is no such sentence as

Re: Unittest test-database not empty

2008-01-29 Thread rock
Thanks Russ, for your helpful comments! I'm now searching for the initial_data fixture. I have looked through all files in this project without success. When I run python manage.py test there is no such sentence as "Loading 'initial_data' fixtures", but maybe there shouldn't be one? I've also

Re: Unittest test-database not empty

2008-01-28 Thread Russell Keith-Magee
On Jan 29, 2008 4:27 AM, rock <[EMAIL PROTECTED]> wrote: > > I'm using the unittesting-environment for test-driven-development in > Django. It works excellent, but one matter is puzzling. The Django > documentation tells me this: > > "The test database > Tests that require a database (namely,

Unittest test-database not empty

2008-01-28 Thread rock
I'm using the unittesting-environment for test-driven-development in Django. It works excellent, but one matter is puzzling. The Django documentation tells me this: "The test database Tests that require a database (namely, model tests) will not use your "real" (production) database. A separate,