问题 PowerMockito：模拟上的NotAMockException

有点复杂的设置。 Robolectric，PowerMockito基于规则的配置。

@RunWith(RobolectricGradleTestRunner.class)
@Config(constants = BuildConfig.class, sdk = 21)
@PowerMockIgnore({"org.mockito.*", "org.robolectric.*", "android.*"})
// Using "PrepareOnlyThis" prevents powermock from trying to instrument the whole hierarchy,
// part of which we've ignored (android.os.* in this case)
@PrepareOnlyThisForTest({ServiceCallbackBase.class}) // this class extends Handler, 
// so we need PrepareOnlyThis.  It also has some final methods we need to verify()
public class ServiceBaseTests {

  private class Foo {
    // nothing
  }

  @Rule
  public PowerMockRule rule = new PowerMockRule();

  private ServiceCallbackBase<Object, Foo> setupCallback( boolean hasValidContext, boolean allContextsCanceled ) {
    ServiceCallbackBase<Object, Foo> callback = PowerMockito.mock( ServiceCallbackBase.class );
    // EDIT:  I have converted these to PowerMockito.doReturn()s to no avail.
    PowerMockito.when( callback.hasValidContext() ).thenReturn( hasValidContext );
    PowerMockito.when( callback.allContextsAreCanceled( any( Message.class ) ) ).thenReturn( allContextsCanceled );
    PowerMockito.doNothing().when( callback ).preSendMessage( any( Message.class ) );
    return callback;
  }

应该是很常规的。但每当我试着打电话 verify 在其中一个“回调”模拟实例上，例如：

  private void test_notifyCallback( boolean isFromCache ) {
    ServiceCallbackBase<Object, Foo> callback = setupCallback( true, false );

    uut.addHandler( TestEnum.FOO, callback );
    uut.addHandler( TestEnum.BAR, PowerMockito.mock( ServiceCallbackBase.class ) );
    uut.addHandler( TestEnum.BAZ, PowerMockito.mock( ServiceCallbackBase.class ) );

    Response<Foo> foo = new Response<>( new Foo(), new ResponseStatus( 0, "Error" ) );
    uut.handleCallBack( TestEnum.FOO, foo, isFromCache );

    ArgumentCaptor<Message> captor = ArgumentCaptor.forClass( Message.class );

    // this line throws the error.  
    verify( callback ).preSendMessage( captor.capture() );

    assertThat( captor.getValue().what ).isEqualTo( TestEnum.FOO.ordinal() );
    assertThat( captor.getValue().obj ).isEqualTo( foo );
    assertThat( captor.getValue().arg1 ).isEqualTo( isFromCache ? 1 : 0 );
  }

我得到一个错误：

org.mockito.exceptions.misusing.NotAMockException: 
Argument passed to verify() is of type ServiceCallbackBase$$EnhancerByMockitoWithCGLIB$$9acf906b and is not a mock!
Make sure you place the parenthesis correctly!
See the examples of correct verifications:
    verify(mock).someMethod();
    verify(mock, times(10)).someMethod();
    verify(mock, atLeastOnce()).someMethod();

显然，显然已被mockito“增强”，而且PowerMock没有使用verify（）方法代替 Mockito.verify()... 是什么赋予了？

编辑：这在某些方面更多，在某些方面不那么令人困惑。

我正在构建另一个测试类来测试ServiceCallbackBase本身。如果我从该类中删除测试，则这些测试通过。不同类中的以下代码段会导致上述测试失败。

@RunWith(RobolectricGradleTestRunner.class)
@Config(constants = BuildConfig.class, sdk = 21)
public class ServiceCallbackBaseTests {

  @Test
  public void test_nothing(){

  }

  private ServiceCallbackBase<Object, String> uutSpy;


  @Before
  public void setup(){
    uutSpy = mock( ServiceCallbackBase.class );
  }
}

5801

2017-12-17 20:24

起源

在这里你会找到答案： stackoverflow.com/questions/29611893/mockito-notamockexception - piotrek1543

你必须更加详细。问题的关键在于它是一个模拟，如堆栈跟踪中的类名中明确指出的： ServiceCallbackBase$$EnhancerByMockitoWithCGLIB$$9acf906b - Jon O

答案:

我无法构建你的例子，但我设法编写了这个产生非常类似问题的minitest：

@RunWith(RobolectricGradleTestRunner.class)
@Config(constants = BuildConfig.class, sdk = 21)
@PowerMockIgnore({"org.mockito.*", "org.robolectric.*", "android.*"})
@PrepareOnlyThisForTest({ServiceCallbackBase.class, Dummy.class})
public class MainActivityTest {

    @Rule
    public PowerMockRule rule = new PowerMockRule();

    @Test
    public void test1() throws Exception {
        try {
            //This Mockito.withSettings() thing is important to make the test fail!
            ServiceCallbackBase callback = PowerMockito.mock( ServiceCallbackBase.class, Mockito.withSettings());

            callback.dispatchMessage(null);
            Mockito.verify(callback).dispatchMessage(null);

        } catch (Exception e){
            e.printStackTrace();
            Assert.fail();
        }
    }
}

（注意Mockito.withSettings（），我不知道为什么会让测试失败）

打印：

org.mockito.exceptions.misusing.NotAMockException: 
    Argument passed to verify() is of type ServiceCallbackBase$$EnhancerByMockitoWithCGLIB$$62776c54 and is not a mock!
    Make sure you place the parenthesis correctly!
    ......

好吧，这绝对看起来像一个类加载问题，mockito正在比较PowerCock加载的ServiceCallbackBase $$ EnhancerByMockitoWithCGLIB $$等与Robolectric加载的相同（显然在该比较中返回false）

然后，我设法让测试工作简单地添加 "org.powermock.*"到了这条线 @PowerMockIgnore... 这是：

@PowerMockIgnore({"org.mockito.*", "org.robolectric.*", "android.*", "org.powermock.*"})

这个简单的改变使我的测试工作，我真的希望你也能做到。

2018-02-22 15:57

我不能给你足够的赞成。我不知道为什么，但那就解决了。谢谢！ - Jon O

我很高兴。别客气！ - fonkap

我有同样的问题，如果暂时解决这个问题。但请确保您添加 "org.powermock.*" 到了 PowerMockIgnore 注释每考试班 - andy9775

谢谢，这就行了！ - Aaron Dancygier

我也遇到了这个问题。 PowerMock项目实际上存在一个问题： https://github.com/jayway/powermock/issues/593

但没有任何一个powermock开发者的评论。

2018-01-28 19:34

问题 PowerMockito：模拟上的NotAMockException

答案:

热门问题