summaryrefslogtreecommitdiff
path: root/docs/topics/testing.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/testing.txt')
-rw-r--r--docs/topics/testing.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt
index 6648461014..a9ba66ece0 100644
--- a/docs/topics/testing.txt
+++ b/docs/topics/testing.txt
@@ -980,19 +980,21 @@ subclass::
def setUp(self):
# Test definitions as before.
+ call_setup_methods()
def testFluffyAnimals(self):
# A test that uses the fixtures.
+ call_some_test_code()
Here's specifically what will happen:
* At the start of each test case, before ``setUp()`` is run, Django will
flush the database, returning the database to the state it was in
- directly after ``syncdb`` was called.
+ directly after :djadmin:`syncdb` was called.
* Then, all the named fixtures are installed. In this example, Django will
install any JSON fixture named ``mammals``, followed by any fixture named
- ``birds``. See the :djadmin:`loaddata documentation<loaddata>` for more
+ ``birds``. See the :djadmin:`loaddata` documentation for more
details on defining and installing fixtures.
This flush/load procedure is repeated for each test in the test case, so you
@@ -1028,6 +1030,7 @@ For example::
def testIndexPageView(self):
# Here you'd test your view using ``Client``.
+ call_some_test_code()
This test case will use the contents of ``myapp.test_urls`` as the
URLconf for the duration of the test case.