4

我看到非常奇怪的行为试图存根在抽象父myMethod(param)类MyClass中定义的类方法MyAbstractBaseClass。

当我尝试存根（使用doReturn("...").when(MyClassMock).myMethod(...)等）此方法失败时，在不同的场景下会引发不同的异常。异常在该行被抛出。

当我使用 doReturn("...").when(MyClassMock).myMethod(CONCRETE PARAM CLASS OBJECT)时，我得到以下异常：

org.mockito.exceptions.misusing.WrongTypeOfReturnValue: 
String cannot be returned by hasValidExpirationDate()
hasValidExpirationDate() should return boolean
    at ...

hasValidExpirationDate()不是被存根的方法，而是由MyMethod(param)抽象基类中的实际实现调用。

当我使用 doReturn("...").when(MyClassMock).myMethod(any(PARAMCLASS.class))时，我得到以下异常：

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: 
Invalid use of argument matchers!
0 matchers expected, 1 recorded.
This exception may occur if matchers are combined with raw values:

， ETC。

但是当我myMethod(param)在子类MyClass中定义方法时，代码不再失败。我的具体实现MyClass只是调用super.myMethod(param)并返回它，所以除了修复单元测试之外它没有任何作用。所以看起来 Mockito 只能在被模拟的类中定义的存根方法，而不是在超类中。

我正在阅读 Mockito 文档，但看不到它在哪里说不能对继承的方法进行存根。

myMethod(param)既不是static也不是final。

代码：

类BaseCard：

import java.io.Serializable;

public class BaseCard implements Serializable {

    public boolean hasValidExpirationDate() {
        return true;
    }
}

类Card：

abstract class Card  extends BaseCard {

    public Card () {    }

    public String getUnexpiredStringForNetwork(){

        //If the date is invalid return empty string, except for Discover.
        if( ! hasValidExpirationDate()){
           return "hi";
        }

        return "hello";
    }
}

类DecryptedCard：

public class DecryptedCard extends Card {

}

类MyTest：

import static org.mockito.Mockito.doReturn;
import static org.mockito.Mockito.mock;

import org.junit.Test;


public class MyTest {

    @Test
    public void test() {
        DecryptedCard decryptedCardMock = mock(DecryptedCard.class);

        doReturn("ABC").when(decryptedCardMock).getUnexpiredStringForNetwork();

    }

}

失败：

org.mockito.exceptions.misusing.WrongTypeOfReturnValue: 
String cannot be returned by hasValidExpirationDate()
hasValidExpirationDate() should return boolean
***
If you're unsure why you're getting above error read on.
Due to the nature of the syntax above problem might occur because:
1. This exception *might* occur in wrongly written multi-threaded tests.
   Please refer to Mockito FAQ on limitations of concurrency testing.
2. A spy is stubbed using when(spy.foo()).then() syntax. It is safer to stub spies - 
   - with doReturn|Throw() family of methods. More in javadocs for Mockito.spy() method.

    at Card.getUnexpiredStringForNetwork(Card.java:10)
    at DecryptedCard.getUnexpiredStringForNetwork(DecryptedCard.java:1)
    at MyTest.test(MyTest.java:13)
    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:601)
    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)
4

2 回答 2

1

根据这个 SO answer，当父类是非公开的时，不能保证模拟行为，如issue 212中所述。

（感谢 Brice 在另一个线程中的好答案，并感谢 Vladimir、JB Nizet 和 acdcjunior 在评论线程中分享调试进度！）

于 2013-12-02T18:05:17.473 回答
0

哇！就是这样！

我遇到了奇怪的异常：

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

-> at com.medziku.motoresponder.logic.ExposedResponder.createSettings(ResponderTest.java:163)
-> at com.medziku.motoresponder.logic.ExposedResponder.createSettings(ResponderTest.java:163)

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"))

虽然一切都是正确的。我试图从模拟类的超类模拟方法，而这个超类与模拟类在同一个文件中，所以它不是公共的，并且会出现那些奇怪的错误。将超类移动到单独的文件并将其设置为公开后，问题就消失了！

于 2016-07-28T00:03:35.443 回答