From 94bd4abf19950e9533624236d2d99045338c0839 Mon Sep 17 00:00:00 2001 From: gfyoung Date: Tue, 2 May 2017 12:24:54 -0400 Subject: [PATCH] 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. --- doc/source/contributing.rst | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/doc/source/contributing.rst b/doc/source/contributing.rst index 08e28582e7469d..d304d21c5c4577 100644 --- a/doc/source/contributing.rst +++ b/doc/source/contributing.rst @@ -633,12 +633,7 @@ framework that will facilitate testing and developing. Thus, instead of writing .... 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 -using test classes allows for better organization. However, instead of inheriting from ``tm.TestCase``, we should just inherit from ``object``: - -.. code-block:: python - - class TestReallyCoolFeature(object): - .... +using test classes allows for better organization. If test classes are used, make sure that they do inherit from ``tm.TestCase``. Using ``pytest`` ~~~~~~~~~~~~~~~~