Adjust verify timeouts in unit test

apache · Feb 24, 2020 · c225588 · c225588
1 parent 31996a0
commit c225588
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/core/src/test/java/com/datastax/oss/driver/internal/core/pool/ChannelPoolShutdownTest.java b/core/src/test/java/com/datastax/oss/driver/internal/core/pool/ChannelPoolShutdownTest.java
@@ -71,7 +71,7 @@ public void should_close_all_channels_when_closed() throws Exception {
     inOrder.verify(eventBus, VERIFY_TIMEOUT.times(1)).fire(ChannelEvent.channelClosed(node));
 
     // Reconnection should have kicked in and started to open channel4, do not complete it yet
-    verify(reconnectionSchedule).nextDelay();
+    verify(reconnectionSchedule, VERIFY_TIMEOUT).nextDelay();
     factoryHelper.waitForCalls(node, 1);
 
     CompletionStage<Void> closeFuture = pool.closeAsync();
@@ -138,7 +138,7 @@ public void should_force_close_all_channels_when_force_closed() throws Exception
     inOrder.verify(eventBus, VERIFY_TIMEOUT.times(1)).fire(ChannelEvent.channelClosed(node));
 
     // Reconnection should have kicked in and started to open a channel, do not complete it yet
-    verify(reconnectionSchedule).nextDelay();
+    verify(reconnectionSchedule, VERIFY_TIMEOUT).nextDelay();
     factoryHelper.waitForCalls(node, 1);
 
     CompletionStage<Void> closeFuture = pool.forceCloseAsync();