@Mock annotation instead of PowerMockito.mock(Mocked.class)?

[glenviewjeff]

I much prefer the readability of the annotated style of Mockito declarations like: @Mock Editable editable;

However I have some static/final classes that seem to require the @PrepareForTest( { Editable.class}) and editable = PowerMockito.mock(Editable.class); style code.

Is there any support in PowerMock for using the @Mock or alternate annotations in place of the PowerMockito.mock() calls?

[Johan Haleby]

You need to use @PrepareForTest( { Editable.class})but then you can use @Mock Editable editable to create and inject a mock instance. If I remember things correctly It only works instance mocks and not "static mocks".

/Johan

--
You received this message because you are subscribed to the Google Groups "PowerMock" group.
To view this discussion on the web visit https://groups.google.com/d/msg/powermock/-/Y3c0Zm1RRUUydThK.
To post to this group, send email to powe...@googlegroups.com.
To unsubscribe from this group, send email to powermock+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/powermock?hl=en.

[glenviewjeff]

The @Mock annotation appears not to work (I assume as designed) for final classes.  It sure would be nice if there were a @PowerMock or @FinalMock annotation that would perform the functional equivalent to editText = PowerMockito.mock(EditText.class);

[Johan Haleby]

It should already work. Have a look at the examples here.

/Johan

On 06/06/2011 04:28 PM, glenviewjeff wrote:

The @Mock annotation appears not to work (I assume as designed) for final classes.  It sure would be nice if there were a @PowerMock or @FinalMock annotation that would perform the functional equivalent to editText = PowerMockito.mock(EditText.class);

--
You received this message because you are subscribed to the Google Groups "PowerMock" group.

To view this discussion on the web visit https://groups.google.com/d/msg/powermock/-/T3VuMV9yc3BFQm9K.

[glenviewjeff]

Johan, thanks so much for getting back to me!  I'm not sure if this is a bug or a feature, but it ended up that the reason for the failures was that in my @Before SetUp() method I was calling

MockitoAnnotations.initMocks(this);

Which apparently causes the final mocking to fail.  Maybe this could be mentioned somewhere in the documentation if it can't somehow be deprecated to prevent developers from inadvertently calling it.

I had started this project with Mockito and didn't realize this call needs to be removed for PowerMock+Mockito.

Jeff

[Johan Haleby]

Ah I see, you're absolutely right that calling initMocks from Mockito will override the mocks created by PowerMock. Glad you sorted it out.

/Johan

--
You received this message because you are subscribed to the Google Groups "PowerMock" group.

To view this discussion on the web visit https://groups.google.com/d/msg/powermock/-/Slp5UERtNTV4b0VK.

[John Rix]

I am able to get the @Mock annotation working by adding classes to the PrepareForTest annotation as suggested. However, the RETURNS_DEEP_STUBS answer appears to no longer be effective and I see NullPointerExceptions when creating mock responses for deep stub invocations eg.

        @Mock(answer = Answers.RETURNS_DEEP_STUBS) CloseableHttpResponse mockResponse;

@Before

public void setup() {

                when(mockResponse.getStatusLine().getStatusCode()).thenReturn(HttpStatus.SC_OK);

        }

Anyone else had this problem?

Thanks,

John

[Johan Haleby]

Probably a bug. Would be great if someone could provide a pull request.

To unsubscribe from this group and stop receiving emails from it, send an email to powermock+...@googlegroups.com.

To post to this group, send email to powe...@googlegroups.com.

Visit this group at http://groups.google.com/group/powermock.
For more options, visit https://groups.google.com/d/optout.