CompletableFuture 和 MockMVC答案

【问题标题】：CompletableFuture and MockMVCCompletableFuture 和 MockMVC
【发布时间】：2018-11-13 14:47:08
【问题描述】：

我正在使用 SpringBoot 2.0.6-RELEASE

当我将我的 api 配置为使用没有提供执行程序服务的 CompletableFuture 时 - 我的测试成功运行。例如这个测试通过了 ok

public Future<List<AlertsBodyVO>> getAlerts(@PathVariable(value = "userId") final String userId) {
        return CompletableFuture.supplyAsync(() -> Service.getAlerts(userId));
    }


    @Test
    public void testGetAlerts_NullResult() throws Exception {
        String userId = "123456";

        List<AlertsBodyVO> alertsVOList = null;     

        Mockito.when(mockService.getAlerts(Mockito.anyString())).thenReturn(alertsVOList);

        MvcResult result = this.mockMvc.perform(get("/alerts/{userId}",  userId)).andExpect(status().isOk())
                .andReturn();

        mockMvc.perform(asyncDispatch(result)).andExpect(status().isOk())
                .andExpect(jsonPath("$").doesNotExist())
                .andReturn();        

        Mockito.verify(mockService, Mockito.times(1)).getAlerts(Mockito.anyString());
    }

但是 - 当我将我的 api 定义为使用 executorService 时，如下所示

public Future<List<AlertsBodyVO>> getAlerts(@PathVariable(value = "userId") final String userId) {
        return CompletableFuture.supplyAsync(() -> Service.getAlerts(userId), executorService);
    }

我收到以下错误

java.lang.IllegalStateException: Async result for handler [public java.util.concurrent.Future<java.util.List<com.domain.AlertsBodyVO>> com.controllers.API.getAlerts(java.lang.String)] was not set during the specified timeToWait=10000
at org.springframework.test.web.servlet.DefaultMvcResult.getAsyncResult(DefaultMvcResult.java:146)
at org.springframework.test.web.servlet.DefaultMvcResult.getAsyncResult(DefaultMvcResult.java:136)
at org.springframework.test.web.servlet.request.MockMvcRequestBuilders.asyncDispatch(MockMvcRequestBuilders.java:269)
at com.controllers.APITest.testGetAlerts_NullResult(APITest.java:207)
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:498)
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.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
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.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.mockito.internal.runners.DefaultInternalRunner$1.run(DefaultInternalRunner.java:78)
at org.mockito.internal.runners.DefaultInternalRunner.run(DefaultInternalRunner.java:84)
at org.mockito.internal.runners.StrictRunner.run(StrictRunner.java:39)
at org.mockito.junit.MockitoJUnitRunner.run(MockitoJUnitRunner.java:161)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)

知道当我指定要使用的 executorService 时如何让我的 MockMvc 测试通过吗？

【问题讨论】：

你使用什么样的executorService？我按照您提供的方式编写了测试，没有出现任何错误
我使用了 Executor 接口 - 它被模拟用于测试

标签： spring-boot executorservice spring-test threadpoolexecutor mockmvc

【解决方案1】：

Mocked ExecuterService 很难使用，因为你还应该模拟他们所有的行为，比如

Mockito.when(mockedExecuterService.execute...

还有另一个隐藏在执行器服务内部的调用和进程。取而代之的是，您可以仅为测试目的创建简单的单线程执行程序，我进行了检查，它与真正的ExecutorService（例如Executors.newSingleThreadExecutor()）一起工作正常，并且在模拟时失败了。我想你现在知道如何创建测试上下文 - Spring Test Context

【讨论】：