diff options
| author | Berker Peksag <berker.peksag@gmail.com> | 2018-08-03 21:56:55 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-03 21:56:55 (GMT) |
| commit | 2e5566d9e774dcde81e8139b486730917816e045 (patch) | |
| tree | 7d2c73da72dad196470788f028542bf6d658020c | |
| parent | d8078626770a8d358eb83d7928c12d75ff4e821a (diff) | |
| download | cpython-2e5566d9e774dcde81e8139b486730917816e045.zip cpython-2e5566d9e774dcde81e8139b486730917816e045.tar.gz cpython-2e5566d9e774dcde81e8139b486730917816e045.tar.bz2 | |
Fix reST markup in unittest documentation (GH-8665)
| -rw-r--r-- | Doc/library/unittest.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst index 086d937..224adf0 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 |