如何验证是否使用 Mockito 调用了两种方法之一?

2022-01-14 00:00:00 mockito java

假设我有一个类有两个我不关心的方法被称为...

Suppose I have a class with two methods where I don't care which is called...

public class Foo {
    public String getProperty(String key) {
        return getProperty(key, null);
    }
    public String getProperty(String key, String defaultValue) {
        //...
    }
}

以下两个(来自另一个类，仍在我的应用程序中)都应该通过我的测试:

Both the below (from another class, still in my application) should pass my test:

public void thisShouldPass(String key) {
    // ...
    String theValue = foo.getProperty(key, "blah");
    // ...
}

public void thisShouldAlsoPass(String key) {
    // ...
    String theValue = foo.getProperty(key);
    if (theValue == null) {
        theValue = "blah";
    }
    // ...
}

我不在乎调用了哪个，我只想调用两个变体之一.

I don't care which was called, I just want one of the two variants to be called.

在 Mockito 中，我通常可以这样做:

In Mockito, I can generally do things like this:

Mockito.verify(foo, atLeastOnce()).getProperty(anyString());

或者:

Mockito.verify(foo, atLeastOnce()).getProperty(anyString(), anyString());

是否有一种本地方式来表示验证其中一个或另一个至少发生了一次"?

Is there a native way to say "verify either one or the other occurred at least once"?

或者我必须做一些粗暴的事情:

Or do I have to do something as crude as:

try {
    Mockito.verify(foo, atLeastOnce()).getProperty(anyString());
} catch (AssertionError e) {
    Mockito.verify(foo, atLeastOnce()).getProperty(anyString(), anyString());
}

推荐答案

您可以将 atLeast(0) 与 ArgumentCaptor 结合使用:

You could use atLeast(0) in combination with ArgumentCaptor:

ArgumentCaptor<String> propertyKeyCaptor = ArgumentCaptor.forClass(String.class);
Mockito.verify(foo, atLeast(0)).getProperty(propertyKeyCaptor.capture(), anyString());

ArgumentCaptor<String> propertyKeyCaptor2 = ArgumentCaptor.forClass(String.class);
Mockito.verify(foo, atLeast(0)).getProperty(propertyKeyCaptor2.capture());

List<String> propertyKeyValues = propertyKeyCaptor.getAllValues();
List<String> propertyKeyValues2 = propertyKeyCaptor2.getAllValues();

assertTrue(!propertyKeyValues.isEmpty() || !propertyKeyValues2.isEmpty()); //JUnit assert -- modify for whatever testing framework you're using

相关文章