Re: Running tests - minor problem with fixtures

2007-05-31 Thread Don Arbow
Well, just a follow up for future spelunkers to this list. Updating my code to the changes in 5173 and 5211 worked (it now loads fixtures that are not named initial_data.json). For some reason, straight code from 0.96 doesn't work, I never figured out why. And I patched get_sql_flush() to use

Re: Running tests - minor problem with fixtures

2007-05-29 Thread Don Arbow
On Tuesday, May 29, 2007, at 05:25 PM, Russell Keith-Magee wrote: > The only other cause I can think of would be an error in the fixture > file that might be getting eaten by the test process. Does the fixture > load ok if you run './manage.py loaddata myfixture' (where myfixture > is the name of

Re: Running tests - minor problem with fixtures

2007-05-29 Thread Russell Keith-Magee
On 5/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > The original question was never really answered. Apologies for that. > I am using 0.96 and cannot load any fixture unless it is named > 'initial_data.json', even when I add a fixtures attribute to my > testcase (yes, it is subclassed f

Re: Running tests - minor problem with fixtures

2007-05-29 Thread donarb
The original question was never really answered. I am using 0.96 and cannot load any fixture unless it is named 'initial_data.json', even when I add a fixtures attribute to my testcase (yes, it is subclassed from django.test.TestCase). My testing works great, as long as I put all my data into ini

Re: Running tests - minor problem with fixtures

2007-04-19 Thread Russell Keith-Magee
On 4/19/07, jararaca <[EMAIL PROTECTED]> wrote: > > > The most likely cause I can think of is that your test extends > > unittest.TestCase, not django.test.TestCase. > > Yes, you're right indeed. I have corrected this but still the fixture > is not found + the tests now take 3 minutes instead of h

Re: Running tests - minor problem with fixtures

2007-04-19 Thread jararaca
> The most likely cause I can think of is that your test extends > unittest.TestCase, not django.test.TestCase. Yes, you're right indeed. I have corrected this but still the fixture is not found + the tests now take 3 minutes instead of half a second. I think I'll stick to the "initial_data" vari

Re: Running tests - minor problem with fixtures

2007-04-19 Thread Russell Keith-Magee
On 4/19/07, jararaca <[EMAIL PROTECTED]> wrote: > > Is this an error in the documentation, a future feature or did I miss > anything? Hi Micha, The most likely cause I can think of is that your test extends unittest.TestCase, not django.test.TestCase. The fixture list is only loaded if your unit

Running tests - minor problem with fixtures

2007-04-19 Thread jararaca
I just tried to run tests with a fixture as described in the documentation. I put an xml dump of my database in der/fixtures (der is my application dir) and run the tests as described in the documentation with manage.py test der But: The fixture is only found if I call it "initial_data" although