Ticket #1814: Testing-patch-1814

--- Testing.txt 2008-04-16 18:20:17.000000000 -0700
+++ Testing-rev.txt     2008-04-28 20:40:59.000000000 -0700
@@ -200,9 +200,12 @@
 probably need a separate database for testing. To make this simpler, TurboGears
 provides the ``testutil.DBTest`` class.
 
-If you inherit from this class, TG will create and drop all the tables in your
-model for each method. In the example below, ``test_model_reset()`` is working
-on a completely empty database despite coming after ``test_name()``.
+If you inherit from this class, and you are using 
+`SQLObject <1.0/SQLObject>`_, TG will provide ``setUp()`` and ``tearDown()`` 
+methods that create and drop all the tables in your model for each method. 
+In the example below, ``test_model_reset()`` is working on a completely empty 
+database despite coming after ``test_name()``, thanks to the ``setUp()`` and
+``tearDown()`` methods inherited from ``testutil.DBTest``.
 
 ::
 
@@ -227,6 +230,38 @@
               assert len(entry) is 0
 
 
+If you want to define your own ``setUp()`` and/or ``tearDown()`` make
+sure that you call those methods from the parent class or you'll get
+``OperationalError: no such table: ...`` exceptions.
+
+::
+
+      from turbogears import testutil
+      from projectname import model
+
+      class TestMyURL(testutil.DBTest):
+          model = model
+
+         def setUp(self):
+             """Pre-test setup.
+
+             Use the parent class setUp() method to create database tables,
+             then ...
+             """
+             super(TestMyURL, self).setUp()
+             # Additional set-up code
+
+
+         def tearDown(self):
+             """Post-test tear-down.
+
+             Use parent class tearDown() method to reset database
+             before next test.
+             """
+             super(TestMyURL, self).tearDown()
+             # Additional tear-down code
+
+
 Other Functionality
 ~~~~~~~~~~~~~~~~~~~