程式扎記

This message was edited 17 times. Last update was at 09/10/2022 14:24:01

Overview
In this tutorial, we'll illustrate the various uses of the standard static mock methods of the Mockito API.

As in other articles focused on the Mockito framework (like Mockito Verify or Mockito When/Then), the MyList class shown below will be used as the collaborator to be mocked in test cases:

view plaincopy to clipboardprint?
package mockito.prac.p3;  
  
import java.util.AbstractList;  
  
public class MyList extends AbstractList<String>{  
    @Override  
    public String get(int index) {  
        return null;  
    }  
  
    @Override  
    public int size() {  
        return 1;  
    }  
}  

Simple Mocking
The simplest overloaded variant of the mock method is the one with a single parameter for the class to be mocked:

view plaincopy to clipboardprint?
public static <T> T mock(Class<T> classToMock)  

We'll use this method to mock a class and set an expectation:

view plaincopy to clipboardprint?
MyList listMock = Mockito.mock(MyList.class);  
when(listMock.add(anyString())).thenReturn(false);  

Then we'll execute a method on the mock:

view plaincopy to clipboardprint?
boolean added = listMock.add("abc");  

The following code confirms that we invoked the add method on the mock. The invocation returns a value that matches the expectation we set before:

view plaincopy to clipboardprint?
verify(listMock).add(anyString());  
assertEquals(added, false);  

Mocking With Mock's Name
In this section, we'll cover another variant of the mock method, which is provided with an argument specifying the name of the mock:

view plaincopy to clipboardprint?
public static <T> T mock(Class<T> classToMock, String name)  

Generally speaking, the name of a mock has nothing to do with the working code. However, it may be helpful in debugging, as we use the mock's name to track down verification errors. To ensure the exception message thrown from an unsuccessful verification includes the provided name of a mock, we'll use assertThatThrownBy.

In the following code, we'll create a mock for the MyList class and name it myMock:

view plaincopy to clipboardprint?
MyList listMock = Mockito.mock(MyList.class, "myMock");  

Then we'll set an expectation on a method of the mock and execute it:

view plaincopy to clipboardprint?
when(listMock.add(anyString())).thenReturn(false);  
listMock.add("abc");  

Next, we'll call the verification inside the assertThrows and verify the instance of the exception thrown:

view plaincopy to clipboardprint?
assertThrows(  
        TooFewActualInvocations.class,  
        () -> verify(listMock, times(2)).add(anyString()));  

Further, we can also verify the exception's message that it should contain the information about the mock:

view plaincopy to clipboardprint?
TooFewActualInvocations exception = assertThrows(  
        TooFewActualInvocations.class,  
        () -> verify(listMock, times(2)).add(anyString()));        
assertTrue(exception.getMessage().contains("myMock.add"));  

Mocking With Answer
Here we'll demonstrate the use of a mock variant in which we'll configure the strategy for the mock's answers to interaction at creation time. This mock method's signature in the Mockito documentation looks like the following:

view plaincopy to clipboardprint?
public static <T> T mock(Class<T> classToMock, Answer defaultAnswer)  

Let's start with the definition of an implementation of the Answer interface:

view plaincopy to clipboardprint?
static class CustomAnswer implements Answer<Boolean> {  
    @Override  
    public Boolean answer(InvocationOnMock invocation) throws Throwable {  
        return false;  
    }  
}  

We'll use the CustomAnswer class above for the generation of a mock:

view plaincopy to clipboardprint?
MyList listMock = Mockito.mock(MyList.class, new CustomAnswer());  

If we don't set an expectation on a method, the default answer, configured by the CustomAnswer type, will come into play. In order to prove this, we'll skip over the expectation setting step and jump to the method execution:

view plaincopy to clipboardprint?
boolean added = listMock.add("abc");  

The following verification and assertion confirm that the mock method with an Answer argument worked as expected:

view plaincopy to clipboardprint?
verify(listMock).add(anyString());  
assertFalse(added);  

Mocking With MockSettings
The final mock method we'll cover in this article is the variant with a parameter of the MockSettings type. We use this overloaded method to provide a non-standard mock.

There are several custom settings supported by methods of the MockSettings interface, such as registering a listener for method invocations on the current mock with invocationListeners, configuring serialization with serializable, specifying the instance to spy on with spiedInstance, configuring Mockito to attempt to use a constructor when instantiating a mock with useConstructor, etc.

For convenience, we'll reuse the CustomAnswer class introduced in the previous section to create a MockSettings implementation that defines a default answer.

A MockSettings object is instantiated by a factory method:

view plaincopy to clipboardprint?
MockSettings customSettings = withSettings().defaultAnswer(new CustomAnswer());  

We'll use that setting object in the creation of a new mock:

view plaincopy to clipboardprint?
MyList listMock = Mockito.mock(MyList.class, customSettings);  

Similar to the preceding section, we'll invoke the add method of a MyList instance, and verify that the mock method with a MockSettings argument works as expected:

view plaincopy to clipboardprint?
boolean added = listMock.add("abc");   
  
verify(listMock).add(anyString());  
assertFalse(added);  

Complete Source Code
The full unit test is as below:

view plaincopy to clipboardprint?
package mockito.prac.p3;  
  
import static org.junit.Assert.assertEquals;  
import static org.junit.Assert.assertFalse;  
import static org.junit.Assert.assertThrows;  
import static org.junit.Assert.assertTrue;  
import static org.mockito.ArgumentMatchers.anyString;  
import static org.mockito.Mockito.times;  
import static org.mockito.Mockito.verify;  
import static org.mockito.Mockito.when;  
import static org.mockito.Mockito.withSettings;  
  
import org.junit.jupiter.api.Test;  
import org.mockito.MockSettings;  
import org.mockito.Mockito;  
import org.mockito.exceptions.verification.TooFewActualInvocations;  
import org.mockito.invocation.InvocationOnMock;  
import org.mockito.stubbing.Answer;  
  
class UsingMockMethod {  
  
    @Test  
    void testSimpleMocking() {  
        MyList listMock = Mockito.mock(MyList.class);  
        when(listMock.add(anyString())).thenReturn(false);  
          
        boolean added = listMock.add("abc");  
          
        verify(listMock).add(anyString());  
        assertEquals(added, false);  
    }  
      
    @Test  
    void testMockingWithMockName() {  
        MyList listMock = Mockito.mock(MyList.class, "myMock");  
        when(listMock.add(anyString())).thenReturn(false);  
          
        listMock.add("abc");  
          
        TooFewActualInvocations exception = assertThrows(  
                TooFewActualInvocations.class,  
                () -> verify(listMock, times(2)).add(anyString()));        
        assertTrue(exception.getMessage().contains("myMock.add"));  
    }  
      
    static class CustomAnswer implements Answer<Boolean> {  
        @Override  
        public Boolean answer(InvocationOnMock invocation) throws Throwable {  
            return false;  
        }  
    }  
      
    @Test  
    void testMockingWithAnswer() {  
        MyList listMock = Mockito.mock(MyList.class, new CustomAnswer());  
          
        boolean added = listMock.add("abc");   
          
        verify(listMock).add(anyString());  
        assertFalse(added);  
    }  
      
    @Test  
    void testMockingWithMockSettings() {  
        MockSettings customSettings = withSettings().defaultAnswer(new CustomAnswer());  
        MyList listMock = Mockito.mock(MyList.class, customSettings);  
          
        boolean added = listMock.add("abc");   
          
        verify(listMock).add(anyString());  
        assertFalse(added);  
    }  
}  

程式扎記

標籤

2022年10月8日星期六

[Mockito] Mockito’s Mock Methods

[Git 常見問題] error: The following untracked working tree files would be overwritten by merge

檢舉濫用情形

學習筆記

標籤

2022年10月8日 星期六

[Mockito] Mockito’s Mock Methods

[Git 常見問題] error: The following untracked working tree files would be overwritten by merge

檢舉濫用情形

學習筆記

2022年10月8日星期六