使用PowerMock- EasyMock时意外的方法调用
使用PowerMock- EasyMock时意外的方法调用
提问于 2014-06-23 08:29:39
我的问题似乎是嘲笑的误解。测试代码。
public class CallHandler {
private SqlSessionFactory sessionFactory;
public CallHandler() {
String resource = "mybatis/mybatis-config.xml";
Reader reader;
try {
reader = Resources.getResourceAsReader(resource);
sessionFactory = new SqlSessionFactoryBuilder().build(reader);
}
catch (IOException e) {
e.printStackTrace();
}
}
public String handleRequest(Call call) {
// Some Implementation
}
}考试课
// I have excluded few unnecessary classes from @PrepareForTest for the post.
@RunWith(PowerMockRunner.class)
@PrepareForTest({SqlSessionFactoryBuilder.class, Resources.class, SqlSessionFactory.class, SqlSession.class})
public class TestCase0 extends TestCase{
private SqlSessionFactory mockedSessionFactory = PowerMock.createMock(SqlSessionFactory.class);
private SqlSession mockedSession = PowerMock.createMock(SqlSession.class);
private CallMapper mockedMapper = PowerMock.createMock(CallMapper.class);
private SqlSessionFactoryBuilder mockedSqlSessionFactoryBuilder= PowerMock.createMock(SqlSessionFactoryBuilder.class);
// Others
@Before
public void setUp() {
}
@Test
public void test0 () throws Exception {
mockStatic(CallMapper.class);
mockStatic(SqlSessionFactoryBuilder.class);
mockStatic(Resources.class);
expect(Resources.getResourceAsReader("mybatis/mybatis-config.xml")).andReturn(mockedReader); expectNew(SqlSessionFactoryBuilder.class).andReturn(mockedSqlSessionFactoryBuilder); expect(mockedSqlSessionFactoryBuilder.build(mockedReader)).andReturn(mockedSessionFactory);
expect(mockedSessionFactory.openSession()).andReturn(mockedSession);
// Few more expectations
replayAll();
assertThat(RESULT0).isEqualTo((new CallHandler()).handleRequest(call));
verifyAll();
}
}这种对构建在新SqlSessionFactoryBuilder上的调用的模拟似乎没有生效，因为原来的build()正在被调用，因此出现了错误。堆栈跟踪
java.lang.AssertionError:
Unexpected method call Reader.close();
at org.easymock.internal.MockInvocationHandler.invoke(MockInvocationHandler.java:44)
at org.powermock.api.easymock.internal.invocationcontrol.EasyMockMethodInvocationControl.invoke(EasyMockMethodInvocationControl.java:91)
at org.powermock.core.MockGateway.doMethodCall(MockGateway.java:105)
at org.powermock.core.MockGateway.methodCall(MockGateway.java:168)
at org.apache.ibatis.session.SqlSessionFactoryBuilder.build(SqlSessionFactoryBuilder.java:58)
at org.apache.ibatis.session.SqlSessionFactoryBuilder.build(SqlSessionFactoryBuilder.java:38)
at com.kwench.integration.ivr.CallHandler.<init>(CallHandler.java:48)
at in.kwench.integration.ivr.TestCase0.test0(TestCase0.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:68)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:310)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:88)
at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:96)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.executeTest(PowerMockJUnit44RunnerDelegateImpl.java:294)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTestInSuper(PowerMockJUnit47RunnerDelegateImpl.java:127)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:86)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:207)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:146)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:33)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:45)
at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:104)
at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:53)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)回答 2
Stack Overflow用户
回答已采纳
发布于 2014-06-25 13:05:31
如果没有您正在测试的代码的完整示例和测试类本身，很难确定您的问题会出现在哪里。
尽管如此，我猜您的问题是，您还没有使用静态方法准备类。这些需要在测试类开始时的@PrepareForTest注释中提供。
PowerMock的文档为模拟静态方法提供了以下技巧。我猜你错过了第2点。https://code.google.com/p/powermock/wiki/MockStatic
模拟静态方法 快速总结
- 在测试用例的类级别使用@RunWith(PowerMockRunner.class)注释。
- 在测试用例的类级别使用@PrepareForTest(ClassThatContainsStaticMethod.class)注释。
- 使用PowerMock.mockStatic(ClassThatContainsStaticMethod.class)模拟该类的所有方法。
- 使用PowerMock.replay(ClassThatContainsStaticMethod.class)将类更改为重播模式。
- 使用PowerMock.verify(ClassThatContainsStaticMethod.class)更改类以验证模式。
您还在嘲弄SqlSessionFactoryBuilder的构造函数调用，因此您也需要考虑其中的技巧。https://code.google.com/p/powermock/wiki/MockConstructor
新对象的模拟构造 快速总结
- 在测试用例的类级别使用@RunWith(PowerMockRunner.class)注释。
- 在测试用例的类级别使用@PrepareForTest(ClassThatCreatesTheNewInstance.class)注释。
- 使用PowerMock.createMock(NewInstanceClass.class)创建应该构造的类的模拟对象(让我们称之为mockObject)。
- 使用PowerMock.expectNew(NewInstanceClass.class).andReturn(mockObject)来期待NewInstanceClass.class类型对象的新构造，但返回模拟对象。
- 使用PowerMock.replay(mockObject，NewInstanceClass.class)将模拟对象和类更改为重播模式，或者使用PowerMock.replayAll()方法。
- 使用PowerMock.verify(mockObject，NewInstanceClass.class)更改模拟对象和类以验证模式，或者使用PowerMock.verifyAll()方法。
考虑到这些技巧，我为您正在尝试测试的方法生成了以下测试方法。这个测试通过得很好。
@RunWith(PowerMockRunner.class)
@PrepareForTest({CallHandler.class, SqlSessionFactoryBuilder.class, Resources.class})
public class CallHandlerTest {
private static final String RESULT0 = "";
@Test
public void test0 () throws Exception {
final Reader mockedReader = EasyMock.createMock(Reader.class);
final SqlSessionFactoryBuilder mockedSqlSessionFactoryBuilder = EasyMock.createMock(SqlSessionFactoryBuilder.class);
final SqlSessionFactory mockedSessionFactory = EasyMock.createMock(SqlSessionFactory.class);
PowerMock.mockStatic(SqlSessionFactoryBuilder.class);
PowerMock.mockStatic(Resources.class);
PowerMock.expectNew(SqlSessionFactoryBuilder.class).andReturn(mockedSqlSessionFactoryBuilder);
EasyMock.expect(Resources.getResourceAsReader("mybatis/mybatis-config.xml")).andReturn(mockedReader);
EasyMock.expect(mockedSqlSessionFactoryBuilder.build(mockedReader)).andReturn(mockedSessionFactory);
PowerMock.replayAll();
assertThat(RESULT0).isEqualTo((new CallHandler()).handleRequest(new Call()));
PowerMock.verifyAll();
}
}Stack Overflow用户
发布于 2016-04-26 22:58:24
这是代码覆盖和powermock.mockStatic之间的冲突。
代码覆盖工具$jacocoInit静态方法进入所有类来收集代码覆盖率。在运行测试用例时，mockStatic模拟$jacocoInit静态方法，这将导致预期的静态方法调用。
您可以绕过在静态方法上创建部分模拟的问题，例如PowerMock.mockStaticPartial(TheClass.class，"theStaticMethod")，以便power模拟不会触及$jacocoInit方法。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/24361495
复制相关文章
相似问题
腾讯云开发者
