Clarified some markup in the discussion of fixture loading in testcases.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13610 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
728effcfbd
commit
e0387f7abe
|
@ -1050,23 +1050,25 @@ A fixture is a collection of data that Django knows how to import into a
|
||||||
database. For example, if your site has user accounts, you might set up a
|
database. For example, if your site has user accounts, you might set up a
|
||||||
fixture of fake user accounts in order to populate your database during tests.
|
fixture of fake user accounts in order to populate your database during tests.
|
||||||
|
|
||||||
The most straightforward way of creating a fixture is to use the ``manage.py
|
The most straightforward way of creating a fixture is to use the
|
||||||
dumpdata`` command. This assumes you already have some data in your database.
|
:djadmin:`manage.py dumpdata <dumpdata>` command. This assumes you
|
||||||
See the :djadmin:`dumpdata documentation<dumpdata>` for more details.
|
already have some data in your database. See the :djadmin:`dumpdata
|
||||||
|
documentation<dumpdata>` for more details.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
If you've ever run ``manage.py syncdb``, you've already used a fixture
|
If you've ever run :djadmin:`manage.py syncdb<syncdb>`, you've
|
||||||
without even knowing it! When you call ``syncdb`` in the database for
|
already used a fixture without even knowing it! When you call
|
||||||
the first time, Django installs a fixture called ``initial_data``.
|
:djadmin:`syncdb` in the database for the first time, Django
|
||||||
This gives you a way of populating a new database with any initial data,
|
installs a fixture called ``initial_data``. This gives you a way
|
||||||
such as a default set of categories.
|
of populating a new database with any initial data, such as a
|
||||||
|
default set of categories.
|
||||||
|
|
||||||
Fixtures with other names can always be installed manually using the
|
Fixtures with other names can always be installed manually using
|
||||||
``manage.py loaddata`` command.
|
the :djadmin:`manage.py loaddata<loaddata>` command.
|
||||||
|
|
||||||
Once you've created a fixture and placed it in a ``fixtures`` directory in one
|
Once you've created a fixture and placed it in a ``fixtures`` directory in one
|
||||||
of your :setting:`INSTALLED_APPS`, you can use it in your unit tests by
|
of your :setting:`INSTALLED_APPS`, you can use it in your unit tests by
|
||||||
specifying a ``fixtures`` class attribute on your ``django.test.TestCase``
|
specifying a ``fixtures`` class attribute on your :class:`django.test.TestCase`
|
||||||
subclass::
|
subclass::
|
||||||
|
|
||||||
from django.test import TestCase
|
from django.test import TestCase
|
||||||
|
|
Loading…
Reference in New Issue