On 27.04.20 16:54, John Patrick wrote:
Just did comment regarding typo.
I also advocate Mockito, so also would be recommending that.
It appeared Mockito supported junit v5 earlier than others and
compared to previous versions remove boiler plate setup. Or I missed
those other frameworks supporting junit v5.
PowerMock might be agued that is supports static, but most of the code
i've reviewed just highlight most developer mock static
classes/methods incorrectly and end up just verifying the mock they
create.
Not touched/used JMock or EasyMock for about 10 years so no idea about them.
For me the need to use PowerMock is a hard smell in code base j
Mockito works for almost all cases ..also final classes working via
mockito-inline dependency...also good support via mockito extension for
JUnit Jupiter via @Mock, @InjectMock etc.
JMockit can help (very rare cases) if you need to mock things like
System.currentMillis or Date but that can be handled different most of
the times...
I would suggest to migrate everything which uses EasyMock, PowerMock in
particular and JMock ...to Mockito only ...
Kind regards
Karl Heinz Marbaise
John
On Mon, 27 Apr 2020 at 15:14, Elliotte Rusty Harold <[email protected]> wrote:
Anyone have an opinion on recommending Mockito as our preferred mocking
library?
https://github.com/apache/maven-site/pull/158/files
This doesn't require us to port old unit tests, though we can. Right now we
have a mix of Mockito, JMock, PowerMock, and EasyMock spread out across the
plugins.
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
