6

I am trying to create some tests for a Python program. I am using Python version 2.7.12 so I had to install mock using sudo pip install mock.

According to the documentation and several other sites, I should be able to use the following code to use patch:

import mock     # Also could use from mock import patch
import unittest

class TestCases(unittest.TestCase):
    @mock.patch('MyClass.ImportedClass')   # If using from mock import patch should just be @patch
    def test_patches(self, mock_ImportedClass):
        # Test code...

However, the above code throws the following error:

AttributeError: 'module' object has no attribute 'patch'

After some experimenting in the terminal, it seems quite a few things don't work. For example

>>> import mock

>>> mock.MagicMock
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'MagicMock'

>>> mock.patch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'patch'

>>> mock.Mock
<class mock.Mock at 0x7fdff56b0600>

Interestingly, I can access something called patch using mock.Mock(), but I don't know if this works in the same way and cannot find anything about it in the documentation.

My experience with Python is fairly limited so I'm not sure what might be wrong. I'm fairly certain the right package was installed. Any help on how I can get this working?

Community
  • 1
  • 1
c1moore
  • 1,827
  • 17
  • 27
  • 6
    Did you name a file `mock.py` or something? Check `mock.__file__` and see what it tells you. – user2357112 Aug 17 '16 at 16:41
  • 1
    @user2357112 you were pretty close. There was another file named `mock.py` in one of the directories in the search path for python. Not sure where it came from, but everything seems to compile now after I removed it. Thanks – c1moore Aug 17 '16 at 17:02
  • I had a `mock` subdirectory moved over, and all tests failed with the same error, once I removed the `mock` directory. everythng works. – Gang Feb 02 '18 at 03:10
  • @user2357112 If you want to write an answer, I can mark it as correct so you can get well deserved points. – c1moore May 25 '18 at 19:18

1 Answers1

3

Just for the sake of completeness, I wanted to add the answer, but the credit goes to @user2357112.

If you run into this issue check to make sure you don't have another file named mock.py (or whatever file you're trying to import) either in the same directory or in the search path for python. To confirm you've loaded the correct file, you can check mock.__file_, which is an attribute added automatically by python to your imported files. If you're using the terminal, you can just do something like:

>>> import mock

>>> mock.__file__
'/usr/lib/python2.7/...'

If the file path doesn't match what you expect, you should remove the file being imported from your search path or modify your search path so that the file you want is found first. If neither of those are an option, you need to change the name of the file you're importing (if it's one you define and not a library like mock).

c1moore
  • 1,827
  • 17
  • 27