From b0b45f9a8373f47e96ef6c22d254c984d3b6b3c0 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sun, 24 Jan 2016 15:36:10 -0500 Subject: [PATCH] Fixed #26132 -- Discouraged use of TransactionTestCase.fixtures. --- docs/topics/testing/tools.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 96332d60b8..c70b0b187d 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -1037,9 +1037,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