Pencils Down » JUnit

EasyMock IllegalArgumentException: not a proxy instance

admin — Tue, 05 Apr 2011 17:24:58 +0000

This error is the result of trying to mock a class instead of an interface. In order to mock a class you have to use the class extensions instead.

So, change your code from:

import static org.easymock.EasyMock.*;

To:

import static org.easymock.classextension.EasyMock.*;

I think it’s just historically how EasyMock got developed:

first interfaces like nice Java/Spring/JUnit theory says your supposed to develop,
then normal classes for the working Java programmers of the world.

How to EasyMock a Void Routine

admin — Wed, 23 Mar 2011 17:47:12 +0000

EasyMock, like other JUnit mock testers, allows you to set expectations for method calls on the mocked object. However, the expect() method wants to see a return type from the method call. So, what to do?

A built-in mechanism of EasyMocks is to just “call” the void method in question. For example a commonly mocked object is the HttpSession:
expect(request.getSession()).andReturn(session); expect(session.getAttribute(name)).andReturn(null); session.setAttribute(eq(name), isA(InSession.class)); replay(session); //whatever you are really trying to test verify(session);

Could only be easier if the doc told you this clearly.

JUnit error – java.lang.Exception: No runnable methods

admin — Fri, 03 Apr 2009 20:18:15 +0000

This error is a catchall for anything else that might be wrong with your test class. First make sure any of the below problems are not occurring.

Your unit test code is running JUnit4. At least one test method must have the @Test annotation. Otherwise this error occurs.

If the class you are testing has @Required setters for Spring injections they must be set otherwise JUnit will mask the missing required exception as a no runnable methods exception.

If you are initializing your mock objects outside of the @Begin method you will get this error.

If you are attempting to mock the same class more than once you will get this error.