You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, first off I like your library and I find it quite useful, great job!
I have found a small bug, which has a workaround but is quite odd.
When using the library with Espresso tests, mocking methods will not work if only doAnswer(...) is used.
This applies to the mocks which are injected by Dagger.
So for example in this instance the code inside doAnswer will not be executed:
Hi, I have never seen a problem like this and I can't think of any reason why it should happen :(
It's just another way of defining the mock, it shouldn't change the behaviour.
Do this always happen? Are you using Robolectric?
Thanks for your report
Hi, first off I like your library and I find it quite useful, great job!
I have found a small bug, which has a workaround but is quite odd.
When using the library with Espresso tests, mocking methods will not work if only
doAnswer(...)
is used.This applies to the mocks which are injected by Dagger.
So for example in this instance the code inside
doAnswer
will not be executed:But if we have a simple
when
on the same mock, everything will work as expected:Any idea what is happening, and if this is a known issue?
Thanks in advance!
The text was updated successfully, but these errors were encountered: