From fdf151bbfbd5aed7c860ff212faf711a270544f3 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Thu, 12 Oct 2017 20:54:32 -0700 Subject: [PATCH] [3.6] Improve test suite customization example (GH-3967) Reported by John Gamboa on docs@p.o at https://mail.python.org/pipermail/docs/2017-June/031942.html (cherry picked from commit 925510449984399cf58711843ddfe2e8007c3878) --- Doc/library/unittest.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst index 2099bd1e2e..e52f140029 100644 --- a/Doc/library/unittest.rst +++ b/Doc/library/unittest.rst @@ -402,10 +402,14 @@ you can do it yourself:: def suite(): suite = unittest.TestSuite() - suite.addTest(WidgetTestCase('test_default_size')) - suite.addTest(WidgetTestCase('test_resize')) + suite.addTest(WidgetTestCase('test_default_widget_size')) + suite.addTest(WidgetTestCase('test_widget_resize')) return suite + if __name__ == '__main__': + runner = unittest.TextTestRunner() + runner.run(suite()) + You can place the definitions of test cases and test suites in the same modules as the code they are to test (such as :file:`widget.py`), but there are several advantages to placing the test code in a separate module, such as -- 2.50.1