2014-06-24 66 views
1

我正在爲使用Java 7 WatchService類功能的類進行單元測試。 WatchService類提供了一個take()函數,該函數在下次目錄發生更改時返回一個WatchKey對象。在WatchService上調用下一次take()之前,必須重置WatchKey。驗證Mockito中的交替調用

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) 

什麼是驗證這種行爲規範的方法?

回答

0

通過使用「回答」回調,您可以嘗試使這些方法的「when」子句更復雜一些。在該應答回調中,您可以使用記錄呼叫順序的共享數據結構。 CUT執行完成後,您可以分析記錄的數據的正確性。

+0

感謝這個指針!我會用它。 – user321418