summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2016-01-24 15:36:10 -0500
committerTim Graham <timograham@gmail.com>2016-01-25 06:52:44 -0500
commit41e059de7ccc25307b02de8b7b346b6735673f0a (patch)
tree6fca9e74a6d81541b1c5d51131fc6d4c1cf9ebda
parent5e44348ad79c3a45dc59b9ed92a35d8d190d48e1 (diff)
[1.9.x] Fixed #26132 -- Discouraged use of TransactionTestCase.fixtures.
Backport of b0b45f9a8373f47e96ef6c22d254c984d3b6b3c0 from master
-rw-r--r--docs/topics/testing/tools.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 2b432211ef..fe6eab7838 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -1057,9 +1057,9 @@ Fixture loading
.. attribute:: TransactionTestCase.fixtures
A test case for a database-backed website isn't much use if there isn't any
-data in the database. To make it easy to put test data into the database,
-Django's custom ``TransactionTestCase`` class provides a way of loading
-**fixtures**.
+data in the database. Tests are more readable and it's more maintainable to
+create objects using the ORM, for example in :meth:`TestCase.setUpTestData`,
+however, you can also use fixtures.
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