我有一些使用CompletableFutures的异步调用，我的单元测试失败了。大多数时候它们没有失败，但是偶尔它们可能会失败...我得到的错误消息是：

org.mockito.exceptions.misusing.PotentialStubbingProblem: 
Strict stubbing argument mismatch. Please check:
 - this invocation of 'queryForList' method:
    namedParameterJdbcTemplate.queryForList(
    null,
    MapSqlParameterSource {id=0},
    class java.lang.String
);
...
Typically, stubbing argument mismatch indicates user mistake when writing tests.
Mockito fails early so that you can debug potential problem easily.
However, there are legit scenarios when this exception generates false negative signal:
  - stubbing the same method multiple times using 'given().will()' or 'when().then()' API
    Please use 'will().given()' or 'doReturn().when()' API for stubbing.
  - stubbed method is intentionally invoked with different arguments by code under test
    Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).

我试过使用doReturn().when()，但它仍然给出同样的错误。使用Mockito.lenient()修复了它，但我觉得使用Mockito.verify()方法是解决这个存根/异步问题的正确方法。
添加验证和模拟后返回：

Mockito.verify(namedParameterJdbcTemplate, Mockito.timeout(100).times(1)).queryForList(Mockito.anyString(), Mockito.any(MapSqlParameterSource.class), Mockito.eq(String.class));
        Mockito.verify(namedParameterJdbcTemplate, Mockito.timeout(100).times(1)).query(Mockito.anyString(), Mockito.any(MapSqlParameterSource.class), Mockito.any(BasicMapper.class));

        Mockito.when(namedParameterJdbcTemplate.queryForList(Mockito.anyString(), Mockito.any(MapSqlParameterSource.class), Mockito.eq(String.class))).thenReturn(null);
        Mockito.when(namedParameterJdbcTemplate.query(Mockito.anyString(), Mockito.any(MapSqlParameterSource.class), Mockito.any(BasicMapper.class))).thenReturn(offerEvents);

我收到此错误

Wanted but not invoked:
namedParameterJdbcTemplate.queryForList
...
Actually, there were zero interactions with this mock.

我解决此问题的最佳方法是什么？