Skip to content

Commit 4e00445

Browse files
committed
DOC: Update documentation for TestCase usage
tm.TestCase no longer follows the nosetest idiom, so it is here to stay, so update the documentation to say that we are using it still. Closes gh-15990. [ci skip]
1 parent 54b4971 commit 4e00445

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

doc/source/contributing.rst

+1-6
Original file line numberDiff line numberDiff line change
@@ -633,12 +633,7 @@ framework that will facilitate testing and developing. Thus, instead of writing
633633
....
634634
635635
Sometimes, it does make sense to bundle test functions together into a single class, either because the test file is testing multiple functions from a single module, and
636-
using test classes allows for better organization. However, instead of inheriting from ``tm.TestCase``, we should just inherit from ``object``:
637-
638-
.. code-block:: python
639-
640-
class TestReallyCoolFeature(object):
641-
....
636+
using test classes allows for better organization. If test classes are used, make sure that they do inherit from ``tm.TestCase``.
642637

643638
Using ``pytest``
644639
~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)