diff options
| author | Tim Graham <timograham@gmail.com> | 2014-12-26 13:23:38 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-01-17 09:59:25 -0500 |
| commit | 67235fd4ef1b006fc9cdb2fa20e7bb93b0edff4b (patch) | |
| tree | 7f2cf7cac4185235e3f066caf9ae5854f0f75bdb /docs/topics/testing | |
| parent | f635d759354842e46901ed1ae1be5f5a0b81e567 (diff) | |
Removed support for initial_data fixtures per deprecation timeline.
Diffstat (limited to 'docs/topics/testing')
| -rw-r--r-- | docs/topics/testing/overview.txt | 5 | ||||
| -rw-r--r-- | docs/topics/testing/tools.txt | 12 |
2 files changed, 0 insertions, 17 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 0aca7fb0a4..57bdfaa0ca 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -260,9 +260,6 @@ The initial serialization is usually very quick, but if you wish to exclude some apps from this process (and speed up test runs slightly), you may add those apps to :setting:`TEST_NON_SERIALIZED_APPS`. -Apps without migrations are not affected; ``initial_data`` fixtures are -reloaded as usual. - Other test conditions --------------------- @@ -288,8 +285,6 @@ prepares itself. You can control the level of detail of these messages with the Creating test database... Creating table myapp_animal Creating table myapp_mineral - Loading 'initial_data' fixtures... - No fixtures found. This tells you that the test runner is creating a test database, as described in the previous section. diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index b9755305cb..1f794701be 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -984,18 +984,6 @@ The most straightforward way of creating a fixture is to use the already have some data in your database. See the :djadmin:`dumpdata documentation<dumpdata>` for more details. -.. note:: - - If you've ever run :djadmin:`manage.py migrate<migrate>`, you've - already used a fixture without even knowing it! When you call - :djadmin:`migrate` in the database for the first time, Django - installs a fixture called ``initial_data``. This gives you a way - 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 :djadmin:`manage.py loaddata<loaddata>` command. - .. admonition:: Initial SQL data and testing Django provides a second way to insert initial data into models -- |