Null controller when test with Mockito

Question

I'm testing a controller that needs a Autowired Service.

I read in many place (example Mockito: How to test my Service with mocking?) I need to do it like this

@RunWith(JUnitPlatform.class)
public class AdminControllerTest {

  @Mock
  private AdminService service;

  @InjectMocks
  private AdminController adminController;

  @Test
  public void registerUser() {
    Boolean resultReal = adminController.registerUser();
    assertTrue(resultReal);
  }
}

But it's fail and I see is because the adminController is null

Instead, if I create the controller like this

AdminController adminController = new AdminController();

It works, but then I can inject the mock.

Maybe I'm forgotten something

show the controller definition and include injected dependencies. — Nkosi, Nov 07 '21 at 18:39

score 1 · Accepted Answer · answered Nov 07 '21 at 21:20

Per the documentation for InjectMocks:

MockitoAnnotations.openMocks(this) method has to be called to initialize annotated objects. In above example, openMocks() is called in @Before (JUnit4) method of test's base class. For JUnit3 openMocks() can go to setup() method of a base class. Instead you can also put openMocks() in your JUnit runner (@RunWith) or use the built-in MockitoJUnitRunner.

Thus, either:

call openMocks(this) somewhere before the test is run or
Use @RunWith(MockitoJUnitRunner.class) on the class

Null controller when test with Mockito

1 Answers1