On Thursday, August 8, 2013 12:04:38 PM UTC+2, Jean-Michel Pichavant wrote:
> - Mail original -
>
> > Hi
> > 1) I prefer to use start/stop and not the decorator .
> > 2) mock_play is the name of the module where the code belongs
>
> > Thanks
>
> > Avishay
> > Sent from my iPhone
>
>
>
- Mail original -
> Hi
> 1) I prefer to use start/stop and not the decorator .
> 2) mock_play is the name of the module where the code belongs
> Thanks
> Avishay
> Sent from my iPhone
You should not neeed to refer to the Calc class using mock_play since it is
defined in the very same
Hi
1) I prefer to use start/stop and not the decorator .
2) mock_play is the name of the module where the code belongs
Thanks
Avishay
Sent from my iPhone
On 7 באוג 2013, at 21:01, Jean-Michel Pichavant
wrote:
- Mail original -
Hi
I would like to mock patch the attribute 'calc' in th
- Mail original -
> Hi
> I would like to mock patch the attribute 'calc' in the 'Client' class
> (See code below).
> I have 2 unit tests:
> 1) test1 - that patch an existing instance of 'Client' - it works
> fine.
> 1) test2 - that tries to patch the 'Client' class. My expectation is
> th
Hi
I would like to mock patch the attribute 'calc' in the 'Client' class (See code
below).
I have 2 unit tests:
1) test1 - that patch an existing instance of 'Client' - it works fine.
1) test2 - that tries to patch the 'Client' class. My expectation is that
after the patching, every instance of