p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #25860 -- Documented a transaction leak possiblity in TestCase. 

Thanks Jonas Haag for report and review.
This commit is contained in:
Tim Graham 2015-12-05 17:48:58 -05:00
parent 59b57e672c
commit a5619f7ed3
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/topics/testing/tools.txt
View File

@ -685,13 +685,22 @@ then you should use :class:`~django.test.TransactionTestCase` or
@classmethod
def setUpClass(cls):
super(MyTestCase, cls).setUpClass() # Call parent first
super(MyTestCase, cls).setUpClass()
...
@classmethod
def tearDownClass(cls):
...
super(MyTestCase, cls).tearDownClass() # Call parent last
super(MyTestCase, cls).tearDownClass()
Be sure to account for Python's behavior if an exception is raised during
``setUpClass()``. If that happens, neither the tests in the class nor
``tearDownClass()`` are run. In the case of :class:`django.test.TestCase`,
this will leak the transaction created in ``super()`` which results in
various symptoms including a segmentation fault on some platforms (reported
on OS X). If you want to intentionally raise an exception such as
:exc:`unittest.SkipTest` in ``setUpClass()``, be sure to do it before
calling ``super()`` to avoid this.
TransactionTestCase
~~~~~~~~~~~~~~~~~~~