gradle看起来像这样:
apply plugin: 'com.android.application'
android {
compileSdkVersion 25
buildToolsVersion "25.0.2"
defaultConfig {
applicationId "com.google.developer.taskmaker"
minSdkVersion 19
targetSdkVersion 25
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
configurations.all {
resolutionStrategy {
force 'com.android.support:support-annotations:25.2.0'
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:25.2.0'
compile 'com.android.support:recyclerview-v7:25.2.0'
compile 'com.android.support:design:25.2.0'
compile 'com.android.support:preference-v7:25.2.0'
debugCompile 'im.dino:dbinspector:3.4.1@aar'
// Android JUnit Runner
compile 'com.google.android.gms:play-services-appindexing:8.4.0'
// Android runner and rules support
// add this for intent mocking support
androidTestCompile 'com.android.support.test.espresso:espresso-intents:2.2.2'
// add this for webview testing support
androidTestCompile 'com.android.support.test.espresso:espresso-web:2.2.2'
compile 'com.android.support.test:runner:0.5'
compile 'com.android.support.test:rules:0.5'
compile 'com.android.support.test.espresso:espresso-core:2.2.2'
}单元测试用例看起来像这样
@RunWith(AndroidJUnit4.class)
public class TestClass {
@Rule
public ActivityTestRule<MainActivity> mActivityRule =
new ActivityTestRule<>(MainActivity.class);
@Test
public void buttonClick(){
onView(withId(R.id.fab)).perform(click()).check(matches(isDisplayed()));
}
}错误消息如下:
java.lang.Exception: Custom runner class AndroidJUnit4 should have a public constructor with signature AndroidJUnit4(Class testClass)
at org.junit.runners.model.InitializationError.<init>(InitializationError.java:38)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:111)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
at com.intellij.junit4.JUnit46ClassesRequestBuilder.collectWrappedRunners(JUnit46ClassesRequestBuilder.java:90)
at com.intellij.junit4.JUnit46ClassesRequestBuilder.getClassesRequest(JUnit46ClassesRequestBuilder.java:51)
at com.intellij.junit4.JUnit4TestRunnerUtil.buildRequest(JUnit4TestRunnerUtil.java:91)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:95)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Process finished with exit code -1我已经检查了其他答案,但没有让solution.Please告诉我哪里出了问题。运行这段代码时,我遇到错误
发布于 2017-06-11 05:46:34
原因1:将测试放在错误的文件夹中
通过在Android Studio中使用默认模板创建一个新的应用程序,并将自动生成的ExampleInstrumentedTest从androidTest文件夹复制到test文件夹,可以复制此错误:

下面是错误的样子:

请注意,为了重现这个问题,您还必须错误地向模块级build.gradle添加依赖项

原因2:错误的测试配置
本地单元测试和插入指令的测试具有不同的运行配置。如果单击编辑配置,如下所示:

您应该会在Android Instrumented Tests下看到仪表化测试,在Android JUnit下看到本地单元测试,如下图所示:
对于Android工具测试,配置应如下所示:

对于Android JUnit:

当您运行测试时,Android Studio将为您创建一个运行配置。如果运行配置位于错误的类别中,请检查test和androidTest文件夹是否正确,然后可以从Edit configurations中删除运行配置,然后再次运行测试。如果您设置正确,Android Studio这次将使用正确的运行配置类型。
解释
Android有两种类型的测试:
仪表化测试
仪器测试是为在手持设备或模拟器上运行而设计的测试。在这些测试中,您需要访问Android库的全功能部分(例如,像真正的Context )。这些需要放在androidTest文件夹中,并且这些测试的依赖项(例如,Espresso,com.android.support.test.rules:0.5)将在您的build.gradle中以androidTestCompile为前缀。
以下是一个插装测试的示例:
import android.content.Context;
import android.support.test.InstrumentationRegistry;
import android.support.test.runner.AndroidJUnit4;
import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.assertEquals;
/**
* Instrumentation test, which will execute on an Android device.
*
* @see <a href="http://d.android.com/tools/testing">Testing documentation</a>
*/
@RunWith(AndroidJUnit4.class)
public class ExampleInstrumentedTest {
@Test
public void useAppContext() throws Exception {
// Context of the app under test.
Context appContext = InstrumentationRegistry.getTargetContext();
assertEquals("com.gyaltsab.myapplication", appContext.getPackageName());
}
}本地单元测试
IDE本地单元测试是可以在中运行的测试。它们通常不依赖于标准JVM上不可用的Android库的任何部分(例如,它们不依赖于Context)。这些依赖项放在build.gradle的testCompile部分中。
下面是一个单元测试示例:
import org.junit.Test;
import static org.junit.Assert.*;
/**
* Example local unit test, which will execute on the development machine (host).
*
* @see <a href="http://d.android.com/tools/testing">Testing documentation</a>
*/
public class ExampleUnitTest {
@Test
public void addition_isCorrect() throws Exception {
assertEquals(4, 2 + 2);
}
}请注意,本地单元测试不需要在类声明中使用@RunWith(AndroidJUnit4.class)注释。有关更完整的解释,请参阅the official docs。
发布于 2017-04-26 05:05:50
我也有同样的问题。我在Android studio 2.3.1中工作。我检查了我的运行配置。在Run->Edit Configurations下,我发现我试图作为仪表化测试运行的测试位于Android JUnit测试类别下,即使我在项目的androidTest目录下也有它。我添加了一个Android Instrumented Test (点击角落的加号按钮),并将其设置为指向我试图运行的测试。帮我修好了。
发布于 2017-04-25 16:25:17
尝试将测试文件移动到androidTest文件夹。
https://stackoverflow.com/questions/43171449
复制相似问题