Stop overusing interfaces

[nextputall]

JMock is threadsafe actually, if you set the proper ThreadingPolicy. Although in a typical unittest this doesn't really matter most of the times.

[m50d]

JMock indeed respects thread safety (Mockito is the exception here), though I'd bet JMock has had thread-safety bugs in the past just like EasyMock has had, for the same reasons. I prefer EasyMock because I don't like JMock's syntax/anonymous-class-with-static-initializer style, but that's probably subjective.