My fixtures won't load unless I name them "initial_data". What is the
reason for this?
On Aug 26, 7:02 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Tue, Aug 26, 2008 at 11:18 PM, dchandek <[EMAIL PROTECTED]> wrote:
>
> > After several iterations of running tests on an application (m
On Tue, 2008-09-02 at 18:45 -0700, ballparkfh wrote:
> My fixtures won't load unless I name them "initial_data". What is the
> reason for this?
Based on the complete lack of example code you've provided, it's
difficult to tell. Perhaps post a short example of your TestCase-derived
class so we c
On Tue, Aug 26, 2008 at 11:18 PM, dchandek <[EMAIL PROTECTED]> wrote:
>
> After several iterations of running tests on an application (manage.py
> test myapp), I have these observations which are not really clear in
> the documentation:
>
> 1. All initial_data fixtures (not just those for the test
One more:
4. django.test.TestCase effectively reloads initial_data fixtures with
every test because it calls the flush command.
--David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post
After several iterations of running tests on an application (manage.py
test myapp), I have these observations which are not really clear in
the documentation:
1. All initial_data fixtures (not just those for the tested app) are
always loaded into the test database.
2. Because there is no means to
5 matches
Mail list logo
