<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi,<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">feels like the patch should be like this:<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><test_liba.py><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">@patch('liba.ClassB')<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">overwrite the ClassB that was imported in liba.py<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">*note liba.ClassB might not be the right complete path, you might have some folders you need to traverse or sth, but that's the general idea.<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Best,<div>Zhi An</div></div></div></div>
<br><div class="gmail_quote">On Fri, Apr 17, 2015 at 3:23 PM, Vinicius Kwiecien Ruoso <span dir="ltr"><<a href="mailto:vinicius.ruoso@gmail.com" target="_blank">vinicius.ruoso@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
Thanks for your answer. Unfortunately, this does not work for me.<br>
libB is not importable during the test, and at some point the test try<br>
to import it.<br>
<br>
Let me show a real minimal example:<br>
├── src<br>
│ └── mylib<br>
│ ├── __init__.py<br>
│ ├── liba.py<br>
└── test<br>
└── mylib<br>
├── conftest.py<br>
└── test_liba.py<br>
<br>
8<---------<br>
<liba.py><br>
from mylibB.libb import ClassB<br>
<br>
class ClassA(ClassB):<br>
pass<br>
<br>
<conftest.py><br>
import os<br>
import sys<br>
<br>
_src_path = os.path.join(os.path.dirname(__file__), '..', '..', 'src')<br>
sys.path.insert(0, os.path.abspath(_src_path))<br>
<br>
<test_liba.py><br>
from mock import patch<br>
<br>
@patch('mylibB.libb.ClassB')<br>
def test_classa_instance(mock_classB):<br>
print mock_classB<br>
8<---------<br>
<br>
This fails with: "ImportError: No module named mylibB" while executing<br>
the patch code.<br>
<br>
My real intent on the test_liba.py file was (and for that to work, I<br>
need to mock libb module import at the conftest.py file):<br>
<br>
import mylib.liba<br>
<br>
def test_classa_instance(mock_classB):<br>
print mylib.liba.ClassA()<br>
<br>
<br>
Attached you may find this file structure if you want to run it.<br>
<br>
Just as a note, I'm using Python 2.6 right now. I intend to support<br>
Python 2.7, but not 3.x at this time.<br>
<br>
Thanks again!<br>
Vinicius<br>
<br>
2015-04-17 14:47 GMT-03:00 Zhi An Ng <<a href="mailto:ngzhian@gmail.com">ngzhian@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Hi,<br>
> I believe you can mock out ClassY as such:<br>
><br>
> @patch('liB.ClassY')<br>
> def test_unit_test(self):<br>
> stuff<br>
><br>
><br>
> More info:<br>
> <a href="https://docs.python.org/3.3/library/unittest.mock.html#quick-guide" target="_blank">https://docs.python.org/3.3/library/unittest.mock.html#quick-guide</a><br>
><br>
> Best,<br>
> Zhi An<br>
><br>
> On Fri, Apr 17, 2015 at 1:35 PM, Vinicius Kwiecien Ruoso<br>
> <<a href="mailto:vinicius.ruoso@gmail.com">vinicius.ruoso@gmail.com</a>> wrote:<br>
>><br>
>> Hi!<br>
>><br>
>> I've been using pytest and it is great. There is just one thing that<br>
>> I'm not satisfied with the way I've implemented, that is module level<br>
>> moking.<br>
>><br>
>> My scenario is as follows: libA and libB where libA depends on libB<br>
>> (uses class definition as superclass). Let's assume this code:<br>
>><br>
>> <libA.py><br>
>> from libB import ClassY<br>
>><br>
>> class ClassX(ClassY):<br>
>> pass<br>
>><br>
>> <libB.py><br>
>> class ClassY(object):<br>
>> pass<br>
>><br>
>> Those modules live on different packages/repositories. LibB can be<br>
>> unit tested just fine, but we need to mock libB module to allow libA<br>
>> to be unit tested (libB won't be available in the moment of the test).<br>
>><br>
>> In a conftest.py file in the tests directory of libA, I've managed to<br>
>> mock the module import by mocking sys.modules dictionary, but I did<br>
>> this at the module (global) scope. I was not able to do it with any<br>
>> hook (like pytest_configure), because the tests files are imported<br>
>> before the hook is called. So a test_libA.py file with "import libA"<br>
>> would cause the test to fail.<br>
>><br>
>> Am I doing something wrong or is this really the way to go?<br>
>><br>
>> Greetings,<br>
>> Vinicius<br>
>><br>
>> _______________________________________________<br>
>> testing-in-python mailing list<br>
>> <a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
>> <a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>