summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2018-08-03 15:13:52 -0700
committerBerker Peksag <berker.peksag@gmail.com>2018-08-04 01:13:52 +0300
commit2a2a3f56f510844a5266f74f347a3fa3baee8ba2 (patch)
tree7b8f8b291436d50a20e360281ff64c24fc5d2b82
parent39fcd9949832323b672f7ff05fd1498b8844a329 (diff)
downloadcpython-git-2a2a3f56f510844a5266f74f347a3fa3baee8ba2.tar.gz
Fix reST markup in unittest documentation (GH-8665)
(cherry picked from commit 2e5566d9e774dcde81e8139b486730917816e045) Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
-rw-r--r--Doc/library/unittest.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst
index 086d937825..224adf0856 100644
--- a/Doc/library/unittest.rst
+++ b/Doc/library/unittest.rst
@@ -412,7 +412,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