EasyMock: missing behavior definition for the preceeding method call

最新推荐文章于 2024-08-11 14:08:08 发布

BalonFan

最新推荐文章于 2024-08-11 14:08:08 发布

阅读量3.2k

点赞数 1

CC 4.0 BY-SA版权

文章标签： behavior callback interface exception object class

本文链接：https://blog.csdn.net/BalonFan/article/details/5706915

本文介绍如何使用EasyMock框架正确模拟返回值的方法。当一个类的方法需要被模拟并返回特定值时，应在单元测试中明确指定返回值。文章通过示例说明了如何避免因未设置返回值而引发的IllegalStateException异常。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

If a method of a class which will be mocked by EasyMock did return some value, you should specify the return value explicitly before you use the mock object in your unit test case. Or else EasyMock will complain:

java.lang.IllegalStateException: missing behavior definition for the preceeding method call xxx

An example:

Say we have a interface named Subject which has a member method as follows:

public interface Subject { Callback addObserver(Callback newObserver); }

Then we should use EasyMock to mock this interface in following way:

public void testRegisterObserver() throws Exception { Subject mockSubject = EasyMock.createNiceMock(Subject.class); Callback mockCallback = EasyMock.createNiceMock(Callback.class); EasyMock.expect(mockSubject.addObserver(EasyMock.<Callback>notNull())).andReturn(mockCallback); EasyMock.replay(mockSubject); // Test code here... EasyMock.verify(mockSubject); }

Note the line contains andReturn. If you missed the call to andReturn, EasyMock will throw out the above IllegalStateException.