Mockito
Wed, 02/13/2008 - 15:19 — Szczepan Faber
Java mocking is dominated by expect-run-verify libraries like EasyMock or jMock. Mockito offers simpler and more intuitive approach: you ask questions about interactions after execution. Using mockito, you can verify what you want. Using expect-run-verify libraries you often look after irrelevant interactions.
Mockito has similar syntax to EasyMock, therefore you can refactor safely. Mockito doesn't understand the notion of 'expectation'. There is only stubbing or verifications.
Read more: http://mockito.googlecode.com
Comments
The absolute best
This is the best mocking famework I have ever used. Granted I have only used JMock, but I hand code mocks every day for enterprise java applications. And I reciently started a new project and went through all the mocking libraries mentioned above and the syntax was so horrible I refused to use them. Then I saw this listed here and spent the last few hours trying out some of the (I thought) difficult-to-mock-using-frameworks situations and Mockito worked for all of them.
I am really impressed.
Correction
JMock does not have a record/replay API. In jMock you write a declarative specification of the expectated calls and the framework then checks the actual calls against that specification as the test runs.