Question

我正在为使用Java 7 WatchService类功能的类进行单元测试。 WatchService类提供了一个take（）函数，该函数在下次目录发生更改时返回WatchKey对象。 WatchKey必须在下次在WatchService上调用take（）之前重置。

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

您可以尝试制作＆＃34;当＆＃34;这些方法的条款稍微复杂一点，使用＆＃34;答案＆＃34;打回来。在该回调回调中，您可以使用记录呼叫顺序的共享数据结构。完成CUT的执行后，您可以分析记录的数据的正确性。

验证Mockito中的交替呼叫

1 个答案: