【问题标题】:Mockito exception when Espresso added to project将 Espresso 添加到项目时的 Mockito 异常
【发布时间】:2016-08-28 20:23:36
【问题描述】:

我在我的项目中成功使用了 Mockito,然后我决定添加一些 Espresso 测试(如此处所述:https://developer.android.com/training/testing/ui-testing/espresso-testing.html#build)并且我被卡住了 - 当我将 espresso 添加到我的 build.gradle 时,我遇到了 Mockito 问题。

当 Mockito 工作正常时,我在 build.gradle 中的依赖项,例如我使用 Mockito 的测试通过了:

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:23.4.0'
    testCompile 'junit:junit:4.12'
    //Mockito framework
    testCompile 'org.mockito:mockito-core:1.10.19'
    // https://mvnrepository.com/artifact/org.powermock/powermock-module-junit4
    testCompile group: 'org.powermock', name: 'powermock-module-junit4', version: '1.6.4'
    testCompile 'org.powermock:powermock-api-mockito:1.5.5'
    androidTestCompile ('com.android.support:support-annotations:23.4.0')
    //androidTestCompile ('com.android.support.test.espresso:espresso-core:2.2.2')
}

当我取消注释最后一行以包含 com.android.support.test.espresso:espresso-core:2.2.2 并再次运行我的测试时,其中一些出现以下错误:

java.lang.IllegalAccessError: class org.mockito.internal.creation.jmock.ClassImposterizer$1 cannot access its superclass org.mockito.internal.creation.cglib.MockitoNamingPolicy

    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    at org.mockito.internal.creation.jmock.ClassImposterizer.<clinit>(ClassImposterizer.java:38)
    at org.mockito.internal.creation.CglibMockMaker.createMock(CglibMockMaker.java:23)
    at org.powermock.api.mockito.internal.mockmaker.PowerMockMaker.createMock(PowerMockMaker.java:43)
    at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:33)
    at org.mockito.internal.MockitoCore.mock(MockitoCore.java:59)
    at org.mockito.Mockito.spy(Mockito.java:1368)
    at todolistj.todolist.unittest.CustomClass.size(CustomClass.java:54)

所有失败的测试都在Mockito.spyMockito.mock 方法上失败。比如:

CustomClass1 li1 = Mockito.spy(new CustomClass1(somevar));

View vm= Mockito.mock(View.class);

任何帮助将不胜感激!

【问题讨论】:

  • 您的 Power mock 版本似乎太旧了。 github.com/spring-projects/spring-boot/issues/2606
  • 这不是mockito的问题,而是powermock
  • 非常感谢!那很棒。将 org.powermock:powermock-api-mockito 更改为 1.6.4 解决了问题!如果您将此作为答案发布,我会接受。

标签: android testing mockito android-espresso


【解决方案1】:

这不是Mockito 的问题,而是Powermock,这取决于旧版本的Mockito

更新此库依赖项或从Powermock gradle 依赖项中排除mockito

【讨论】:

    猜你喜欢
    • 2012-04-07
    • 1970-01-01
    • 1970-01-01
    • 2011-02-10
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多