Mocking a final method with PowerMock + EasyMock

Question

I'm trying to mock a call to the final method ResourceBundle.getString(). With PowerMock 1.4.12 and EasyMock 3.1, the call is not being mocked; instead, the "real" method is called.

My test class:

@RunWith(PowerMockRunner.class)
@PrepareForTest(ResourceBundle.class) 
public class TestSuite {
    @Before
    public void setUp() throws Exception {
        ResourceBundle resourceBundleMock = PowerMock.createNiceMock(ResourceBundle.class);
        expect(resourceBundleMock.getString(BundleConstants.QUEUE)).andReturn("Queue");
        PowerMock.replay(resourceBundleMock);

        beanBeingTested.setMessages(resourceBundleMock);
    }
    ...
}

Code in BeanBeingTested:

private ResourceBundle messages;
...
String label = messages.getString(BundleConstants.QUEUE);

Error message:

java.util.MissingResourceException: Can't find resource for bundle $java.util.ResourceBundle$$EnhancerByCGLIB$$e4a02557, key Queue
at java.util.ResourceBundle.getObject(ResourceBundle.java:384)
at java.util.ResourceBundle.getString(ResourceBundle.java:344)
at com.yoyodyne.BeanBeingTested.setUpMenus(BeanBeingTested.java:87)

When I step through the test case, the debugger shows the type of beanBeingTested.messages as "EasyMock for class java.util.ResourceBundle", so the mock is injected correctly. (Also, there's no error on the call to getString() within the expect() call during set up).

With a plain mock instead of a nice mock, I get the following error:

java.lang.AssertionError: 
  Unexpected method call handleGetObject("Queue"): 
    getString("Queue"): expected: 1, actual: 0

Any idea what I'm doing wrong?

Thanks.

Andy · Answer 1 · 2013-05-15T07:11:26.753

3

You are creating an instance using EasyMock. Instead, when working with static methods, you must mock the class (using PowerMock).

It should work like that (tested with EasyMock 3.0 and PowerMock 1.5, though):

@RunWith(PowerMockRunner.class)
@PrepareForTest(ResourceBundle.class) 
public class TestSuite {
    @Before
    public void setUp() throws Exception {
        // mock the class for one method only
        PowerMock.mockStaticNice(ResourceBundle.class, "getString");

        // define mock-behaviour on the class, when calling the static method
        expect(ResourceBundle.getString(BundleConstants.QUEUE)).andReturn("Queue");

        // start the engine
        PowerMock.replayAll();
    }
}

(I'm aware this question is a few months old, but it might help others, though)

edited May 15 '13 at 07:11

answered Jan 29 '13 at 14:04

Andy

1,964
1
15
29

I am also facing the same issue. But this is still not helping. Are you referring to final methods only or static methods ? – Siddharth Dec 15 '14 at 06:17
@Siddharth {{PowerMock.mockStaticNice()}} mocks one static method of a class, but leaves the rest of the methods untouched. If this thread does not help you, you should create a new question, because it seems you are having different issues. – Andy Dec 15 '14 at 08:43
Thanks for your reply @Andy. But the topic of this thread talks about final method but you are talking about static method. Am I missing something? My issue is that there is "public final void" method which I am trying to mock and the test is calling the actual method instead of mock. Is the above issue different from the one I am talking about? Sorry if I missed some point. – Siddharth Dec 15 '14 at 09:12
PowerMock works for final methods, too. I can't test it right now, so I can just point you to the right direction. I had an issue sometime with PowerMock mocking methods of Java-Internals (i.e. {{System.currentTimeMillis()}} - because of the way PowerMock works, it couldn't mock it, so I used _jMockit_, which worked like a charm, but is quite different to use. – Andy Dec 16 '14 at 09:34

score 1 · Answer 2 · answered Apr 19 '13 at 01:18

Try using:

@PrepareForTest({ResourceBundle.class, BeanBeingTested.class})

With only ResourceBundle in the PrepareForTest the mock will work when called directly from your unit test method, but when called from BeanBeingTested you get the real method being used.

Powermock documentation is lacking in this area.

score 0 · Answer 3 · answered Aug 23 '12 at 17:27

Why bother mocking the call to the resource bundle? Generally, I try to avoid mocking the nuts and bolts of java, such as ArrayList, Date, etc. Resource bundles (and MessageFormat.format()) more or less fall into the same category for me. They generally operate on strings which are fundamentals, and if these things are broken or changing their behavior enough to break a test it's definitely something I want to know :)

Just let them grab the string (which presumably is about to be set in the UI, perhaps after . Don't bother to assert the value returned since you don't want edits to the bundle to break your test. If the string gets set on a mock UI component, This is a good place for anyObject(String.class) which correctly expresses the fact you (probably) don't actually care about the specific string displayed.

I also consider it a benefit when the test fails due to a missing message key. THAT I want to know.

Mocking a final method with PowerMock + EasyMock

3 Answers3

Linked