openmock | Intuitive YAML DSL for HTTP , gRPC , Kafka , and AMQP mocks | Pub Sub library

Here is what I've tried and ti works:

in your before method, try adding:

There are two conflicting things happening in your test:

1. You are using Mockito to init a mock implementation via reflection
2. You have ApplicationUserRepository being Spring injected into the Test class via the constructor.

What ends up happening is this:

1. spring injects applicationUserRepository into the constructor param
2. The applicationUserRepository field is set to the spring injected version in the constructor
3. Mockito inits a new applicationUserRepository mock
4. Mockito replaces the applicationUserRespository field with the mock (i.e. goodbye to your handle on the spring bean that your MVC setup is using!)

The easiest way I can think of to fix it is to use @MockBean instead of the @Mock combined with Constructor injection. @MockBean will instruct Spring to create the mock instance for you, use it, and provide it to you in the test.

If you use the @Mock and @InjectMocks annotations, you need to tell Mockito to initialize those mocks, either by adding

You dont pass a method call on a mock to Mockito.when, as error message helpfully says. You are passing a method call on a object you created yourself.

If you need to stub some methods of the object under test, you are looking for a spy.

I am not sure why you want that, but to achieve that you have to move the "List a" to class level in order to "Mock" and return whatever you want. I have below example working, Hope this helps :

Your JSON formated input request body is incorrectly formatted, I will recommend using Map with objectMapper, Map.of is from jdk-9 if you are using lower version you can replacse it by creating another map using new keyword

I see several reasons why this does not work :

A - @Mock alone is not enough to initialize a mock. You need either :

• Call MockitoAnnotations.initMocks() in setup
• Remove @Mock and call Mockito.mock(UserRepository.class) in setup

However I don't think this will be enough, which brings me to :

B - Your controller looks managed by spring, whereas your mocked AutorisationService is not.

I am assuming there that your controller uses an AutorisationService supposedly injected by spring.

You have several options here :

• Option 1 - Don't use spring at all for your test, and manage your controller and service with mockito. This should look like :

I have finally found the solution without using Captor