Java Mockito抛出未完成的VerificationException(可能与本机方法调用有关)
我在运行测试用例时出现以下异常:Java Mockito抛出未完成的VerificationException(可能与本机方法调用有关),java,spring,reflection,mockito,native-methods,Java,Spring,Reflection,Mockito,Native Methods,我在运行测试用例时出现以下异常: org.mockito.exceptions.misusing.UnfinishedVerificationException: Missing method call for verify(mock) here: -> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Example of correct verification: verify(mock).doSo
org.mockito.exceptions.misusing.UnfinishedVerificationException:
Missing method call for verify(mock) here:
-> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Example of correct verification:
verify(mock).doSomething()
Also, this error might show up because you verify either of: final/private/equals()/hashCode() methods.
Those methods *cannot* be stubbed/verified.
at com.bignibouX.tests.repository.member.MemberCachingIntegrationTest.testFindByEmail(MemberCachingIntegrationTest.java:61)
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.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:72)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:81)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:215)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:81)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:60)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:67)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:161)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
测试用例有两个测试,如下所示:
@ActiveProfiles(Profiles.TEST)
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = { FullIntegrationTestConfiguration.class, BaseTestConfiguration.class, MemberCachingIntegrationTest.Config.class })
public class MemberCachingIntegrationTest {
private static final Member MEMBER_ONE = new Member();
private static final Member MEMBER_TWO = new Member();
@Autowired
private MemberRepository memberRepositoryMock;
@After
public void validate() {
validateMockitoUsage();
}
@Test
public void testFindByEmail() {
when(memberRepositoryMock.findByEmail(anyString())).thenReturn(MEMBER_ONE, MEMBER_TWO);
Member firstInvocation = memberRepositoryMock.findByEmail("foo@foo.com");
assertThat(firstInvocation, is(MEMBER_ONE));
Member secondInvocation = memberRepositoryMock.findByEmail("foo@foo.com");
assertThat(secondInvocation, is(MEMBER_ONE));
verify(memberRepositoryMock, times(1)).findByEmail("foo@foo.com");
Member thirdInvocation = memberRepositoryMock.findByEmail("bar@bar.com");
assertThat(thirdInvocation, is(MEMBER_TWO));
verify(memberRepositoryMock, times(1)).findByEmail("bar@bar.com");
}
@Test
public void passingInexistentEmailToSendPasswordResetShouldNotCauseNPE() {
fail("MemberRepository's findByEmail throws NPE if email not found in db! Reason: because cache was set up not to allow null values...");
fail("Appropriate error page not displayed when above NPE is thrown!");
}
@Profile(Profiles.TEST)
@Configuration
static class Config {
@Bean
public MemberRepository memberRepositoryMock() {
return mock(MemberRepository.class);
}
}
}
我的问题有两个:
- 我不确定这里调用了什么:
。。。它与反射和本机方法有关,但在我的例子中是哪种本机方法sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)
- 我的Mockito用法有什么问题
@RooJpaRepository(domainType = Member.class)
public interface MemberRepository {
@Cacheable(value = CacheConfiguration.DATABASE_CACHE_NAME)
Member findByEmail(String email);
@Cacheable(CacheConfiguration.DATABASE_CACHE_NAME)
Member findByToken(String token);
@CacheEvict(value = CacheConfiguration.DATABASE_CACHE_NAME, key = "#result.email")
<S extends Member> S save(S entity);
}
编辑3:需要考虑的另一件事:如果我删除或注释掉测试中的最后一行和拆卸方法,即
verify(memberRepositoryMock, times(1)).findByEmail("bar@bar.com");
及
考试顺利通过
编辑4:实际上,我正在拼命地尝试改编下面的例子:这是在另一篇文章中给我的。我们注意到模拟是自动连接的,测试使用了spring上下文。有人能帮我把测试做好吗?sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)-根据您提供的堆栈跟踪,mockito在报告错误时有点困惑。这实际上与您的问题无关,但无论如何,这是本机的
NativeMethodAccessorImpl.invoke0
(请参阅)。SpringJUnit4ClassRunner运行它,它是如何工作的,没有什么你应该关心的
现在谈谈您真正的问题,正如我在评论中所写的,这是因为Spring将模拟对象包装到代理中。如果你加上
System.out.println(memberRepositoryMock.getClass());
您将在控制台中看到,这不是模拟,而是一些代理。Mockito只能存根mock,所以这就是您收到错误的原因
现在的问题可能是,如何解决这个问题。首先,您的测试实际上不是一个集成测试,因为您试图模拟存储库,而不是真正测试数据访问的行为。在这种情况下,我将放弃使用spring测试,而选择SimpleMockitoJunitRunner
更新:
好的,现在知道它实际上是要测试的缓存,我理解您需要用Spring缓存装饰模拟存储库,并且您的测试实际上是一个集成测试
这是如何做到的。所提到的一点变化,但不使用静态参考。我觉得稍微自然一点
@ActiveProfiles(Profiles.TEST)
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = { FullIntegrationTestConfiguration.class, BaseTestConfiguration.class, MemberCachingIntegrationTest.Config.class })
public class MemberCachingIntegrationTest {
@Autowired
private MemberRepository cachedRepository;
@Autowired
private MockProvider mockProvider;
@After
public void validate() {
validateMockitoUsage();
}
@Test
public void test() {
when(mockProvider.get().findByEmail(anyString())).thenReturn("foo", "bar");
String firstInvocation = cachedRepository.findByEmail("foo@foo.com");
assertThat(firstInvocation, is("foo"));
String secondInvocation = cachedRepository.findByEmail("foo@foo.com");
assertThat(secondInvocation, is("foo"));
verify(mockProvider.get(), times(1)).findByEmail("foo@foo.com");
String thirdInvocation = cachedRepository.findByEmail("bar@bar.com");
assertThat(thirdInvocation, is("bar"));
verify(mockProvider.get(), times(1)).findByEmail("bar@bar.com");
}
@Configuration
static class Config {
private MemberRepository mockRepository = mock(MemberRepository.class);
@Bean
public MemberRepository cachedRepository() {
return mockRepository;
}
@Bean
public MockProvider mockProvider() {
return new MockProvider(mockRepository);
}
}
public static class MockProvider {
private final MemberRepository repository;
public MockProvider(MemberRepository repository) {
this.repository = repository;
}
public MemberRepository get() {
return this.repository;
}
}
}
注意:Repository返回字符串而不是成员,这是一个更清晰的示例您是否也可以发布MemberRepository代码?@macias:我已经发布了MemberRepository(一个spring数据jpa存储库)。+1有趣。似乎spring将您的模拟存储库包装到某个代理中,您不会收到模拟引用,而是无法存根的代理引用。。sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)行怎么样?我真的很困惑。。。什么是本机的?sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)行就是JUnit运行程序,它使用反射来查找测试方法并运行它们。这并不表示您正在使用代理。然而,这并不是说你没有使用代理。正如macias所说,调试测试并找出它的实际类型。谢谢。我已经编辑了我的帖子。需要考虑的一点是,我正在测试Spring缓存,因此需要一个Spring上下文。你知道如何在不实际访问数据库的情况下测试缓存吗?答案在这里。注意,使用static reference技巧@frant.hartm可以确保您正在调用缓存调用,然后验证您的实际模拟被调用了多少次。我还想到了您的第三次编辑,这很奇怪。这可能是某种幸运的巧合,因为缓存调用堆栈中某个地方的实际模拟,只有在明确验证了emockintousage时才会发生异常。我不确定…嗨,马西亚斯。嗯。你所说的“RepositoryDecorator”是什么意思?我找不到这方面的信息…我一定是个白痴-但这是有效的,我真的不知道为什么?有人能解释一下吗?
System.out.println(memberRepositoryMock.getClass());
@ActiveProfiles(Profiles.TEST)
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = { FullIntegrationTestConfiguration.class, BaseTestConfiguration.class, MemberCachingIntegrationTest.Config.class })
public class MemberCachingIntegrationTest {
@Autowired
private MemberRepository cachedRepository;
@Autowired
private MockProvider mockProvider;
@After
public void validate() {
validateMockitoUsage();
}
@Test
public void test() {
when(mockProvider.get().findByEmail(anyString())).thenReturn("foo", "bar");
String firstInvocation = cachedRepository.findByEmail("foo@foo.com");
assertThat(firstInvocation, is("foo"));
String secondInvocation = cachedRepository.findByEmail("foo@foo.com");
assertThat(secondInvocation, is("foo"));
verify(mockProvider.get(), times(1)).findByEmail("foo@foo.com");
String thirdInvocation = cachedRepository.findByEmail("bar@bar.com");
assertThat(thirdInvocation, is("bar"));
verify(mockProvider.get(), times(1)).findByEmail("bar@bar.com");
}
@Configuration
static class Config {
private MemberRepository mockRepository = mock(MemberRepository.class);
@Bean
public MemberRepository cachedRepository() {
return mockRepository;
}
@Bean
public MockProvider mockProvider() {
return new MockProvider(mockRepository);
}
}
public static class MockProvider {
private final MemberRepository repository;
public MockProvider(MemberRepository repository) {
this.repository = repository;
}
public MemberRepository get() {
return this.repository;
}
}
}