Your problem is: scala is not java.
Your implicit assumption is: "that little scala method there gets translated into something similar in Java; and thus I can simply use mockito to deal with that".
Wrong. You are creating a scala object definition here; and if I remember correctly; object in scala ... translates to static in Java (see here for example).
Thus, on a first glance, you probably need to turn to PowerMock(ito) resp. JMockit in order to mock those static elements. (and my usual warning: don't use PowerMock; because mocking static stuff is a bad idea). And as Philipp M is pointing out in his comment: mocking static is really regarded bad practice. You should rather looking into mocking the "trait" side of things here.
So the real answer is: you have to know what you are doing. Mockito is written for java. You can't just assume that anything that you write down in scala and that "looks somehow" like Java can easily be mapped to the concepts that Mockito is doing its work on.
In order to really understand what is going on; you should first have a look at the class files that the scala compiler creates in your case; check out the method signature; and think for yourself: "if I had to call that method in java source code, how would I do that?" and work from there.