From c01807436ab7c1ae9a3f6ecb955b28c2c743c4d2 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Fri, 3 Aug 2018 15:17:15 -0700 Subject: [PATCH] Fix reST markup in unittest documentation (GH-8665) (cherry picked from commit 2e5566d9e774dcde81e8139b486730917816e045) Co-authored-by: Berker Peksag --- Doc/library/unittest.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst index f0de85f76157..16e1049b7a18 100644 --- a/Doc/library/unittest.rst +++ b/Doc/library/unittest.rst @@ -393,7 +393,7 @@ run whether the test method succeeded or not. Such a working environment for the testing code is called a :dfn:`test fixture`. A new TestCase instance is created as a unique test fixture used to execute each individual test method. Thus -`~TestCase.setUp`, `~TestCase.tearDown`, and `~TestCase.__init__` +:meth:`~TestCase.setUp`, :meth:`~TestCase.tearDown`, and :meth:`~TestCase.__init__` will be called once per test. It is recommended that you use TestCase implementations to group tests together -- 2.47.3