如何使用 mockito 验证 JUnit 测试中对模拟服务的两次连续调用?

Question

我正在使用Spring 4.3.8.RELEASE，JUnit 4.12和Mockito 1.10.18。 我正在尝试测试我的"发布事件"方法是否从下面调用......

@Service
@Transactional
public class MyObjectServiceImpl implements MyObjectService, ApplicationEventPublisherAware
{
    private ApplicationEventPublisher publisher;
    @Override
    public void setApplicationEventPublisher(ApplicationEventPublisher publisher) 
    {
        this.publisher = publisher;
    }
    ...
    public void myMethod(MyObject obj) {
    ...
            publisher.publishEvent(new ThirdPartyUpdateUserEvent(userId));
            publisher.publishEvent(new ThirdPartyUpdateObjectEvent(objectId));

然后在我的 JUnit 测试中，我有

@Before
public final void setup()
{
    eventPublisher = Mockito.mock(ApplicationEventPublisher.class);
    ((ApplicationEventPublisherAware) myObjectService).setApplicationEventPublisher(eventPublisher);
    ((ApplicationEventPublisherAware) userService).setApplicationEventPublisher(eventPublisher);
}   // setup
@Test
...
       // Verify first call
    final ArgumentCaptor<ThirdPartyUpdateUserEvent> argument2 = ArgumentCaptor.forClass(ThirdPartyUpdateUserEvent.class);
    Mockito.verify(eventPublisher, Mockito.times(2)).publishEvent(argument2.capture());
    Assert.assertEquals("Failed to call method with proper argument.", userId, argument2.getValue().getUserId());
    // Verify second call
    final ArgumentCaptor<ThirdPartyUpdateMyObjectEvent> argument = ArgumentCaptor.forClass(ThirdPartyUpdateMyObjectEvent.class);
    Mockito.verify(eventPublisher, Mockito.times(2)).publishEvent(argument.capture());
    Assert.assertEquals("Failed to call method with proper argument.", objectId, argument.getValue().getObjectId());        

通过调试，我可以看到每个"publishEvent"方法只调用一次，但是当我去验证调用时，我收到@Test中第一个"验证"行的错误

java.lang.ClassCastException: org.mainco.subco.ThirdPartyItem.domain.ThirdPartyUpdateMyObjectEvent cannot be cast to org.mainco.subco.ThirdPartyItem.domain.ThirdPartyUpdateUserEvent
    at com.follett.fdr.lycea.lms.MyObject.test.service.MyObjectServiceDWRTest.testArchiveMyObject(MyObjectServiceDWRTest.java:1234)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

验证对模拟发布服务的连续两次调用的正确方法是什么？

Answer 1

而不是为 ThirdPartyUpdateUserEvent 和 第三方更新我的对象事件，为什么不为 Object 创建一个捕获器：

final ArgumentCaptor<Object> argumentsCaptor = ArgumentCaptor.forClass(Object.class);

或者更好的是，无论第三方更新用户事件和第三方更新我的对象事件实现什么通用接口(第三方更新事件？

现在您可以执行此操作：

Mockito.verify(eventPublisher, Mockito.times(2)).publishEvent(argumentsCaptor.capture());
List<Object> arguments = argumentsCaptor.getAllValues();
assertTrue(arguments.get(0) instanceof ThirdPartyUpdateUserEvent);
assertTrue(arguments.get(1) instanceof ThirdPartyUpdateMyObjectEvent);

并针对您需要的任何其他条件测试这些参数。