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 from django.test.TestCase). My testing
> works great, as long as I put all my data into initial_data.json.
>
> Is there anything that would prevent other *.json fixtures from
> loading? My testcase had no setUp() method, but just in case, I added
> one and it still had no effect.

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 you fixture)?

Failing that:
- What is your fixture called?
- Where is it located relative to your project?
- Can you provide a sample test case that doesn't work for you?

To answer your other question: The test case doesn't need to have a
setUp() method, just a fixtures=[] definition.

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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to