That a particular method on a foreign object is called is the domain of integration tests and not unit tests, although poor design can lead the boundaries of those two mind sets to blur. In my opinion, your test should strive to never test the interaction between a mock and your test code and it is the fault of Java that is an unavoidable side effect of modern design patterns.

Making your mocks more explicit seems to be the antitheses of their point. They are an unfortunate necessity that should only been seen and heard when something has gone wrong. Mockito excels at this.