#13851: Clarification of the 'Fixture loading' section of the unit test
documentation
------------------------------------+---------------------------------------
Reporter: igloo | Owner: nobody
Status: closed | Milestone:
Component: Documentation | Version: 1.2
Resolution: invalid | Keywords: fixtures, testing
framework, unit tests, initial_data
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
The provided example is completely correct. Test fixtures don't need to be
called initial_data. If your fixture is named "initial_data" it will be
loaded as a default fixture as part of the syncdb process.
If you're having difficulty loading fixtures that aren't called
initial_data, then something else is going wrong. Please ask on django-
users to debug the problem you are having.
Given that this appears to be a case of user error, I'm closing invalid.
If it turns out that there is something that needs to be clarified, we can
reopen once the problem has been established.
--
Ticket URL: <http://code.djangoproject.com/ticket/13851#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
