mockito provides the capability to a reset a mock so that it can be reused later. take a look at the following code snippet.

//reset mock
reset(calcservice);

here we've reset mock object. mathapplication makes use of calcservice and after reset the mock, using mocked method will fail the test.

example

step 1 − create an interface called calculatorservice to provide mathematical functions

file: calculatorservice.java

public interface calculatorservice {
   public double add(double input1, double input2);
   public double subtract(double input1, double input2);
   public double multiply(double input1, double input2);
   public double divide(double input1, double input2);
}

step 2 − create a java class to represent mathapplication

file: mathapplication.java

public class mathapplication {
   private calculatorservice calcservice;

   public void setcalculatorservice(calculatorservice calcservice){
      this.calcservice = calcservice;
   }
   
   public double add(double input1, double input2){
      return calcservice.add(input1, input2);		
   }
   
   public double subtract(double input1, double input2){
      return calcservice.subtract(input1, input2);
   }
   
   public double multiply(double input1, double input2){
      return calcservice.multiply(input1, input2);
   }
   
   public double divide(double input1, double input2){
      return calcservice.divide(input1, input2);
   }
}

step 3 − test the mathapplication class

let's test the mathapplication class, by injecting in it a mock of calculatorservice. mock will be created by mockito.

file: mathapplicationtester.java

package com.tutorialspoint.mock;

import static org.mockito.mockito.mock;
import static org.mockito.mockito.when;
import static org.mockito.mockito.reset;

import org.junit.assert;
import org.junit.before;
import org.junit.test;
import org.junit.runner.runwith;
import org.mockito.runners.mockitojunitrunner;

// @runwith attaches a runner with the test class to initialize the test data
@runwith(mockitojunitrunner.class)
public class mathapplicationtester {
	
   private mathapplication mathapplication;
   private calculatorservice calcservice;

   @before
   public void setup(){
      mathapplication = new mathapplication();
      calcservice = mock(calculatorservice.class);
      mathapplication.setcalculatorservice(calcservice);
   }

   @test
   public void testaddandsubtract(){

      //add the behavior to add numbers
      when(calcservice.add(20.0,10.0)).thenreturn(30.0);
  
      //test the add functionality
      assert.assertequals(mathapplication.add(20.0, 10.0),30.0,0);

      //reset the mock	  
      reset(calcservice);

      //test the add functionality after resetting the mock
      assert.assertequals(mathapplication.add(20.0, 10.0),30.0,0);   
   }
}

step 4 − execute test cases

create a java class file named testrunner in c:\> mockito_workspace to execute test case(s).

file: testrunner.java

import org.junit.runner.junitcore;
import org.junit.runner.result;
import org.junit.runner.notification.failure;

public class testrunner {
   public static void main(string[] args) {
      result result = junitcore.runclasses(mathapplicationtester.class);
      
      for (failure failure : result.getfailures()) {
         system.out.println(failure.tostring());
      }
      
      system.out.println(result.wassuccessful());
   }
}  	

step 5 − verify the result

compile the classes using javac compiler as follows −

c:\mockito_workspace>javac calculatorservice.java mathapplication.
   java mathapplicationtester.java testrunner.java

now run the test runner to see the result −

c:\mockito_workspace>java testrunner

verify the output.

testaddandsubtract(mathapplicationtester): expected:<0.0> but was:<30.0>
false