PPet | 👻 Put a cute girl on your desktop , a little more fun 😏~ | State Container library

I have a handful of very similar projects, all Java, SpringBoot, and Maven. All of them have one class with the same name, and almost identical contents. I added an additional method in one of them, the class with the problem I'm going to describe, but I'm pretty sure that detail is a coincidence.

Each project also has a test class corresponding to that very similar class, and the skeleton of that test class is identical in each class. The test class has an @InjectMocks for the class under test (CUT), and two @Mock annotations, one of which corresponds to an instance variable of the CUT.

The test class does have a @Before method that creates an instance variable used by the tests.

All the variations of the test class have "@RunWith(MockitoJUnitRunner.class)".

If I run one of the "good" tests and set a breakpoint on the first line of the @Before method and then look at the "this" variables in the variables pane, I see the types of the two @Mock-ed instance variables end with "$MockitoMock".

If I do the same thing in the "bad" test, the types of the two @Mock-ed variables do NOT end with "$MockitoMock". In fact, these appear to be normal instances of the corresponding classes, not mocked classes.

Even more curious, in the "bad" test, I tried making explicit calls to "instvar = mock(clazz.class)" in the @Before method, and after I step over those, the type of the instance variable is STILL not a mocked type, HOWEVER, when I click on the instance variable, the toString panel shows "Mock for ..., hashCode: 1028811481". If I "Resume" at this point, I can hit a breakpoint in the allegedly mocked class, with that same instance whose toString value says "Mock for ...".

That's the issue in words. Now I guess I'll show some code.

Here's part of the "bad" test class: