JSR 303 bean validation unit testing with Mockito and Autowiring

Question

I want to junit test my validator class but my validator class has @autowired service classes. How do I inject these dependencies using Mocikto?

I am going to call the

Answer 1

To achieve this I created custom ConstraintValidatorFactory to provide my custom ConstraintValidator.

Assume we have the following:

1. SomeValidation - Bean Validation constraint annotation
2. SomeValidationValidator - Bean Validation constraint validator with @Autowired dependencies. It contains two constructors: default and the one that takes dependencies

Now you can create a test SomeValidationValidatorTest that implements ConstraintValidatorFactory and is run with MockitoJUnitRunner.class:

@RunWith(MockitoJUnitRunner.class)
public class SomeValidationValidatorTest implements ConstraintValidatorFactory {
    @Mock
    private MyDependency myDependencyMock;
}

You must implement getInstance method from ConstraintValidatorFactory:

@Override
public > T getInstance(Class key) {
    if (key == SomeValidationValidator.class) {
        return (T) new SomeValidationValidator(myDependencyMock);
    }
    throw new IllegalArgumentException("expecting SomeValidationValidator!");
}

Having this you can configure the Validator:

@Before
public void setUp() throws Exception {

    // see https://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html/chapter-bootstrapping.html#_constraintvalidatorfactory
    Configuration config = Validation.byDefaultProvider().configure();
    config.constraintValidatorFactory(this);

    ValidatorFactory factory = config.buildValidatorFactory();

    validator = factory.getValidator();
}

In the end create some test:

@Test
public void someTest1() {
    // arrange
    Bean bean = new Bean();
    Mockito.when(myDependencyMock.isValid(null)).thenReturn(true);
    // act
    Set> constraintViolations = validator.validate(bean);
    // assert
    Assert.assertTrue(constraintViolations.isEmpty());
    Mockito.verify(myDependencyMock).isValid(null);
}

The above solution is not perfect but I assume it gives you the idea of using custom ConstraintValidatorFactory to solve the problem.