From b31daff1f77c071b36b43bf874befd7c66e55342 Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Sat, 2 Apr 2016 04:32:06 +0300 Subject: Issue #26688: Fix module name in mock docs Patch by Ashley Anderson. --- Doc/library/unittest.mock-examples.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/library/unittest.mock-examples.rst b/Doc/library/unittest.mock-examples.rst index ac7fce0..0bb52ef 100644 --- a/Doc/library/unittest.mock-examples.rst +++ b/Doc/library/unittest.mock-examples.rst @@ -359,7 +359,7 @@ The module name can be 'dotted', in the form ``package.module`` if needed: A nice pattern is to actually decorate test methods themselves: - >>> class MyTest(unittest2.TestCase): + >>> class MyTest(unittest.TestCase): ... @patch.object(SomeClass, 'attribute', sentinel.attribute) ... def test_something(self): ... self.assertEqual(SomeClass.attribute, sentinel.attribute) @@ -372,7 +372,7 @@ If you want to patch with a Mock, you can use :func:`patch` with only one argume (or :func:`patch.object` with two arguments). The mock will be created for you and passed into the test function / method: - >>> class MyTest(unittest2.TestCase): + >>> class MyTest(unittest.TestCase): ... @patch.object(SomeClass, 'static_method') ... def test_something(self, mock_method): ... SomeClass.static_method() @@ -382,7 +382,7 @@ passed into the test function / method: You can stack up multiple patch decorators using this pattern: - >>> class MyTest(unittest2.TestCase): + >>> class MyTest(unittest.TestCase): ... @patch('package.module.ClassName1') ... @patch('package.module.ClassName2') ... def test_something(self, MockClass2, MockClass1): -- cgit v0.12