2017-03-01 36 views
0

我试图删除从一个依赖模块:可访问性测试的框架的Android gradle这个排除模块不能正常工作

org.robolectric:robolectric:3.2.2使用

com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework:2.1 

com.android .support.test.espresso:浓咖啡的contrib:2.2.2使用

com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework:2.0 

我gradle这个文件看起来像这样:

compile 'com.android.support.test.espresso:espresso-core:2.2.2' 


testCompile ("org.robolectric:robolectric:3.2.2") { 
    exclude module: 'accessibility-test-framework' 
} 

我可以看到错误:

Warning:Conflict with dependency 'com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework'. Resolved versions for app (2.0) and test app (2.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details. 

当我cd到应用程序的工作目录,并大跳

./gradlew -q app:dependencies 

请参阅最后一行:

_mockDebugUnitTestCompile - ## Internal use, do not manually configure ## 
+--- com.android.support:support-annotations:25.1.1 
+--- com.android.support:design:25.1.1 
| +--- com.android.support:support-v4:25.1.1 
| | +--- com.android.support:support-compat:25.1.1 
| | | \--- com.android.support:support-annotations:25.1.1 
| | +--- com.android.support:support-media-compat:25.1.1 
| | | +--- com.android.support:support-annotations:25.1.1 
| | | \--- com.android.support:support-compat:25.1.1 (*) 
| | +--- com.android.support:support-core-utils:25.1.1 
| | | +--- com.android.support:support-annotations:25.1.1 
| | | \--- com.android.support:support-compat:25.1.1 (*) 
| | +--- com.android.support:support-core-ui:25.1.1 
| | | +--- com.android.support:support-annotations:25.1.1 
| | | \--- com.android.support:support-compat:25.1.1 (*) 
| | \--- com.android.support:support-fragment:25.1.1 
| |   +--- com.android.support:support-compat:25.1.1 (*) 
| |   +--- com.android.support:support-media-compat:25.1.1 (*) 
| |   +--- com.android.support:support-core-ui:25.1.1 (*) 
| |   \--- com.android.support:support-core-utils:25.1.1 (*) 
| +--- com.android.support:appcompat-v7:25.1.1 
| | +--- com.android.support:support-annotations:25.1.1 
| | +--- com.android.support:support-v4:25.1.1 (*) 
| | +--- com.android.support:support-vector-drawable:25.1.1 
| | | +--- com.android.support:support-annotations:25.1.1 
| | | \--- com.android.support:support-compat:25.1.1 (*) 
| | \--- com.android.support:animated-vector-drawable:25.1.1 
| |   \--- com.android.support:support-vector-drawable:25.1.1 (*) 
| +--- com.android.support:recyclerview-v7:25.1.1 
| | +--- com.android.support:support-annotations:25.1.1 
| | +--- com.android.support:support-compat:25.1.1 (*) 
| | \--- com.android.support:support-core-ui:25.1.1 (*) 
| \--- com.android.support:transition:25.1.1 
|   +--- com.android.support:support-annotations:25.1.1 
|   \--- com.android.support:support-v4:25.1.1 (*) 
+--- org.mockito:mockito-core:2.0.111-beta 
| +--- net.bytebuddy:byte-buddy:1.4.17 
| \--- org.objenesis:objenesis:2.4 
+--- org.powermock:powermock-api-mockito:1.6.1 
| +--- org.mockito:mockito-all:1.10.8 
| \--- org.powermock:powermock-api-support:1.6.1 
|   +--- org.powermock:powermock-core:1.6.1 
|   | +--- org.powermock:powermock-reflect:1.6.1 
|   | | \--- org.objenesis:objenesis:2.1 -> 2.4 
|   | \--- org.javassist:javassist:3.18.2-GA 
|   \--- org.powermock:powermock-reflect:1.6.1 (*) 
+--- org.powermock:powermock-module-junit4-rule-agent:1.6.1 
| +--- org.powermock:powermock-module-javaagent:1.6.1 
| | \--- org.powermock:powermock-core:1.6.1 (*) 
| \--- org.powermock:powermock-core:1.6.1 (*) 
+--- org.powermock:powermock-module-junit4-rule:1.6.1 
| +--- org.powermock:powermock-classloading-base:1.6.1 
| | +--- org.powermock:powermock-api-support:1.6.1 (*) 
| | \--- org.powermock:powermock-reflect:1.6.1 (*) 
| \--- org.powermock:powermock-core:1.6.1 (*) 
+--- org.powermock:powermock-module-junit4:1.6.1 
| +--- junit:junit:4.12 
| | \--- org.hamcrest:hamcrest-core:1.3 
| \--- org.powermock:powermock-module-junit4-common:1.6.1 
|   +--- junit:junit:4.4 -> 4.12 (*) 
|   +--- org.powermock:powermock-core:1.6.1 (*) 
|   \--- org.powermock:powermock-reflect:1.6.1 (*) 
+--- org.robolectric:robolectric:3.2.2 
| +--- org.robolectric:robolectric-annotations:3.2.2 
| +--- org.robolectric:robolectric-resources:3.2.2 
| | +--- org.robolectric:robolectric-utils:3.2.2 
| | | +--- org.ow2.asm:asm:5.0.1 
| | | +--- org.ow2.asm:asm-commons:5.0.1 
| | | | \--- org.ow2.asm:asm-tree:5.0.1 
| | | |   \--- org.ow2.asm:asm:5.0.1 
| | | +--- org.robolectric:robolectric-annotations:3.2.2 
| | | \--- com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework:2.1 

任何想法?

回答

1

您在应用程序和测试中使用了不同的版本。

可以使用强制库在您的应用程序:

compile 'com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework:2.1.0' 

或者可以使用咖啡框架仅在测试,以避免该问题:

androidTestcompile 'com.android.support.test.espresso:espresso-core:2.2.2' 
+0

嗨Gabtiele,感谢您的评论。我有另一个关于移动espresso核心到android testcompile的问题 - > http://stackoverflow.com/questions/42510579/android-androidtestcompile-espresso-core-causing-filenotfoundexception-r-txt – Killesk

+0

但是,我试过你的第一个答案它的工作原理。你需要把最后的.0出来 - >编译'com.google.android.apps.common.testing.accessibility.framework:accessibility-test-framework:2。 – Killesk

+0

嘿,你在编译范围中声明了测试依赖项,你确定吗? –