hello, Ivano!

how can I help you today>

er, today?

sorry for the delay

but the boss was speaking with me

Good <getMarkTime> you used CountDownLatch to test Retrofit 1 in your nice book

With Mockito

yes

I would like to know if the choice to use CountDownlatch was dictated by the fact of simulating delayed server responses

and if you ever heard of MockWebServer Library that according to someone in SO is quite used

I have heard of MockWebServer; I have not used it and cannot comment on it

OK

in terms of CountDownLatch, you need to do something to have your test thread wait for asynchronous results

I see

I tend to use CountDownLatch for that

I am sure that there are other java.util.concurrent approaches that would work as well

OK

so basically Mockito have to be used when I am going to test a method that has a dependency

giving to that object a default behaviour

so that I can junit test the behaviour

there are other mock libraries that you could consider (e.g., PowerMock)

And I can combine Mockito with UI espresso tests in jacoco is that correct?

PowerMock is good to test private methods

AFAIK that is possible, but I have not used Mockito with instrumentation tests

yep is tricky to use instrumentation and junit togheter

and always related to retrofit, as my code won the black belt of big ball of mud champions league... retrofit has onResponse where are attached some callbacks to the anonymous class with the results

it makes readable the code to move the anonymous class of retrofit in another class making the method static, or should I maintain the anonymous class?

I cannot really answer that

I do not know your code and cannot comment on whether something makes that code more readable

make sense is like reading a poem, there is a lot of subjectivity involved

OK thanks

that is a wrap for today's chat

the transcript will be available from https://commonsware.com/office-hours/ shortly

OK thanks

the next chat is Tuesday, also at 9am US Eastern

have a pleasant day!

you too