org.mockito.exceptions.misusing.InvalidUseOfMatchersException嘗試創建自定義參數匹配器時

Question

我正在使用Mockito 1.10.18。我試圖創建具有以下簽名的方法自定義的參數匹配...

SaveResult[] com.sforce.soap.enterprise.EnterpriseConnection.update(SObject[] sObjects) throws ConnectionException 

我寫了下面的自定義參數匹配...

class AccountMatcher extends ArgumentMatcher<SObject[]> 
{ 
    private Set<String> idList = new HashSet<String>(); 
    AccountMatcher(final Set<Account> mainList) 
    { 
     for (final Account acct : mainList) 
     { 
      idList.add(acct.getId()); 
     } // for 
    } 

    public boolean matches(Object param) 
    { 
     final SObject[] compSet = ((SObject[]) param); 
     final Set<String> compIdList = new HashSet<String>(); 
     for (final SObject acct : compSet) 
     { 
      compIdList.add(acct.getId()); 
     } // for 
     return Util.twoSetsMatch(compIdList, idList); 
    } // matches 
} 

然而，當我嘗試設置此在我的JUnit測試...

final Set<Account> firstBatch = new HashSet<Account>(); 
    firstBatch.add(acct); 
    final SObject[] firstBatchAccts = Matchers.argThat(new AccountMatcher(firstBatch)); 
    Mockito.verify(mockConnection, Mockito.times(1)).update(firstBatchAccts); 

我出現以下情況例外，當我運行它...

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: 
Misplaced argument matcher detected here: 

-> at org.mainco.subco.sf.repo.AccountDaoIT.testUpdateAccountMaxRowsReached(AccountDaoIT.java:129) 

You cannot use argument matchers outside of verification or stubbing. 
Examples of correct usage of argument matchers: 
    when(mock.get(anyInt())).thenReturn(null); 
    doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject()); 
    verify(mock).someMethod(contains("foo")) 

Also, this error might show up because you use argument matchers with methods that cannot be mocked. 
Following methods *cannot* be stubbed/verified: final/private/equals()/hashCode(). 
Mocking methods declared on non-public parent classes is not supported. 

    at org.mainco.subco.sf.repo.AccountDaoIT.testUpdateAccountMaxRowsReached(AccountDaoIT.java:130) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:497) 
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) 
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) 
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) 
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) 
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74) 
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83) 
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88) 
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) 
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) 
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) 
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) 
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) 
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) 
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71) 
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363) 
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174) 
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) 
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) 

Answer 1

這是因爲你已經提取firstBatchAccts（Matcher調用的結果）給變量而不是方法。 argThat和所有其他Mockito匹配器work via side-effects，所以他們必須在恰當的時間被調用。

verify檢查一堆空匹配器，然後重新設置模擬器的期望，以免它們干擾驗證。一些匹配器調用發生，然後對要驗證的方法的調用完成該過程：清除堆棧，檢查發生的方法調用，並將模擬切換回您的存根行爲（如果有的話）。

你有它的方式，argThat被調用，然後調用verify發生，verify檢查沒有發生未使用的匹配器調用。這會觸發你的例外。

相反，內聯調用：

verify(mockConnection).update(argThat(new AccountMatcher(firstBatch))); 

...或者使一個方法調用代替，這使順序正確：

public SObject[] arrayMatchingAccounts(Set<Account> accountSet) { 
    return argThat(new AccountMatcher(accountSet)); 
} 

verify(mockConnection).update(arrayMatchingAccounts(firstBatch));