驗證Mockito中的交替呼叫

Question

我正在為使用Java 7 WatchService類功能的類進行單元測試。 WatchService類提供了take（）函數，該函數將在下一次目錄更改時返回WatchKey對象。 下一次在WatchService上調用take（）之前，必須重置WatchKey。

Mockito提供了一個InOrder類來幫助解決這類問題，但是它似乎不能在反復交替的情況下很好地發揮作用。

我最大的努力

for(int i = 1; i < 4; i++){
    inOrder.verify(mockWatcher, atLeast(i)).take();
    inOrder.verify(mockKey, atLeast(i)).reset();
}
inOrder.verify(mockWatcher, times(4)).take(); // the last take() is interrupted before returning

失敗並顯示錯誤

org.mockito.exceptions.verification.VerificationInOrderFailure: 
Verification in order failure
Wanted but not invoked:
watchKey.reset();
-> at com.co3.examples.Co3DirectoryWatcherTest.run_noProblems_performActionsCorrectly(Co3DirectoryWatcherTest.java:273)
Wanted anywhere AFTER following interaction:
watchService.take();
-> at com.co3.examples.Co3DirectoryWatcher.run(Co3DirectoryWatcher.java:78)

    at com.co3.examples.Co3DirectoryWatcherTest.run_noProblems_performActionsCorrectly(Co3DirectoryWatcherTest.java:273)
    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:45)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
    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)

驗證此行為的規范方法是什么？

Answer 1

您可以嘗試使用“ Answer”回調使這些方法的“ when”子句更加復雜。 在該Answer回調中，您可以利用共享的數據結構來記錄調用的順序。 完成CUT的執行后，您可以分析記錄的數據的正確性。