【发布时间】:2016-01-24 21:30:26
【问题描述】:
我在检测的 Android 单元测试中使用 JUnit4 @BeforeClass 注释时遇到问题(我正在使用 Espresso GUI 测试库)。一旦我添加了带有 @BeforeClass 注释的测试,Android Studio 1.5.1 根本不会运行任何测试,而只会打印“空测试套件”。我没有使用测试套件。我搜索了这个网站和网络,但找不到解决方案。我认为在@BeforeClass 方法中调用的代码实际上失败(TDD)可能是一个问题,但是当将在正常测试用例中工作的代码放入@BeforeClass 时,甚至会发生此错误带注释的方法。
谢谢。
更新:在检查 logcat 输出后,正如一位评论者所建议的那样,问题似乎在于没有启动任何活动:未找到任何活动。您是否忘记通过调用getActivity() 或startActivitySync 或类似名称来启动活动?
我应该怎么做?我不能使用ActivityTestRule 字段,因为@BeforeClass 注释方法是静态的。
也许我只是以错误的方式使用了@BeforeClass 注释。我的印象是,您可以使用此注释在测试类中的所有其他测试之前执行测试。我基本上是在这里寻找 TestNG 注释 "dependsOnMethods" 的替代品。也许我最好在测试类上使用@FixMethodOrder(MethodSorters.NAME_ASCENDING) 注释并将第一个测试用例重命名为aaa_my_testcase。
有人可以对此发表评论吗?谢谢。
改写了问题的标题。
import android.support.test.rule.ActivityTestRule;
import android.support.test.runner.AndroidJUnit4;
import org.junit.BeforeClass;
import org.junit.FixMethodOrder;
import org.junit.Rule;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.MethodSorters;
import static android.support.test.espresso.Espresso.onView;
import static android.support.test.espresso.Espresso.pressBack;
import static android.support.test.espresso.action.ViewActions.click;
import static android.support.test.espresso.assertion.ViewAssertions.matches;
import static android.support.test.espresso.matcher.ViewMatchers.isDisplayed;
import static android.support.test.espresso.matcher.ViewMatchers.isEnabled;
import static android.support.test.espresso.matcher.ViewMatchers.withContentDescription;
import static android.support.test.espresso.matcher.ViewMatchers.withId;
import static android.support.test.espresso.matcher.ViewMatchers.withText;
import static org.hamcrest.CoreMatchers.allOf;
import static org.hamcrest.CoreMatchers.not;
@RunWith(AndroidJUnit4.class)
public class MainActivityTest {
@Rule
public ActivityTestRule<MainActivity> menuActivityTestRule = new ActivityTestRule<>(MainActivity.class);
private static void checkSignBrowserIsDisplayed() {
onView(withText(R.string.sign_browser)).check(matches(isDisplayed()));
}
@BeforeClass
public static void checkSignBrowserIsDisplayedOnAppStartup() {
checkSignBrowserIsDisplayed();
}
build.app:
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
buildToolsVersion "23.0.2"
defaultConfig {
applicationId "foo"
minSdkVersion 15
targetSdkVersion 23
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
debug {
debuggable true
}
}
testOptions {
unitTests.returnDefaultValues = true
}
}
dependencies {
testCompile 'org.mockito:mockito-core:1.10.19'
testCompile 'junit:junit:4.12'
androidTestCompile 'junit:junit:4.12'
androidTestCompile 'com.android.support:support-annotations:23.1.1'
androidTestCompile 'com.android.support.test:runner:0.4.1'
androidTestCompile 'com.android.support.test:rules:0.4.1'
androidTestCompile 'org.hamcrest:hamcrest-library:1.3'
androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.1'
// required if you want to use Mockito for Android instrumentation tests - not needed now.
// androidTestCompile 'org.mockito:mockito-core:1.+'
// androidTestCompile "com.google.dexmaker:dexmaker:1.2"
// androidTestCompile "com.google.dexmaker:dexmaker-mockito:1.2"
compile fileTree(include: ['*.jar'], dir: 'libs')
compile 'org.apache.commons:commons-lang3:3.4'
compile 'com.android.support:appcompat-v7:23.1.1'
compile 'com.android.support:design:23.1.1'
}
测试输出:
运行测试
测试运行开始完成
空测试套件。
Logcat 输出:
01-25 10:22:42.746 22098-22118/foo I/TestRunner: run started: 5 tests
01-25 10:22:42.764 22098-22118/foo D/InputManagerEventInjectionStrategy: Creating injection strategy with input manager.
01-25 10:22:42.890 22098-22118/foo I/TestRunner: failed: foo.MainActivityTest
01-25 10:22:42.890 22098-22118/foo I/TestRunner: ----- begin exception -----
01-25 10:22:42.891 22098-22118/foo I/TestRunner: java.lang.RuntimeException: No activities found. Did you forget to launch the activity by calling getActivity() or startActivitySync or similar?
at android.support.test.espresso.base.RootViewPicker.waitForAtLeastOneActivityToBeResumed(RootViewPicker.java:189)
at android.support.test.espresso.base.RootViewPicker.findRoot(RootViewPicker.java:134)
at android.support.test.espresso.base.RootViewPicker.get(RootViewPicker.java:80)
at android.support.test.espresso.ViewInteractionModule.provideRootView(ViewInteractionModule.java:69)
at android.support.test.espresso.ViewInteractionModule_ProvideRootViewFactory.get(ViewInteractionModule_ProvideRootViewFactory.java:23)
at android.support.test.espresso.ViewInteractionModule_ProvideRootViewFactory.get(ViewInteractionModule_ProvideRootViewFactory.java:9)
at android.support.test.espresso.base.ViewFinderImpl.getView(ViewFinderImpl.java:68)
at android.support.test.espresso.ViewInteraction$2.run(ViewInteraction.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5312)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:901)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:696)
01-25 10:22:42.891 22098-22118/foo I/TestRunner: ----- end exception -----
01-25 10:22:42.891 22098-22118/foo I/TestRunner: failed: Test mechanism
01-25 10:22:42.892 22098-22118/foo I/TestRunner: ----- begin exception -----
01-25 10:22:42.892 22098-22118/foo I/TestRunner: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.os.Bundle.putString(java.lang.String, java.lang.String)' on a null object reference
at android.support.test.internal.runner.listener.InstrumentationResultPrinter.reportFailure(InstrumentationResultPrinter.java:183)
at android.support.test.internal.runner.listener.InstrumentationResultPrinter.testFailure(InstrumentationResultPrinter.java:173)
at org.junit.runner.notification.SynchronizedRunListener.testFailure(SynchronizedRunListener.java:63)
at org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:142)
at org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
at org.junit.runner.notification.RunNotifier.fireTestFailures(RunNotifier.java:138)
at org.junit.runner.notification.RunNotifier.fireTestFailure(RunNotifier.java:132)
at org.junit.internal.runners.model.EachTestNotifier.addFailure(EachTestNotifier.java:23)
at org.junit.runners.ParentRunner.run(ParentRunner.java:369)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)
at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:240)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1928)
【问题讨论】:
-
你检查过你的 LogCat 输出了吗?通常有一个异常,堆栈跟踪被打印在那里
-
好点!有一个我一直在寻找的例外。
-
java.lang.RuntimeException:未找到活动。您是否忘记通过调用 getActivity() 或 startActivitySync 或类似方法启动 Activity? 但是,我应该如何启动 Activity?我不能使用 menuActivityTestRule,因为 @BeforeClass 注解的方法是静态的。
-
我不知道,因为我不进行活动测试,但您应该用您的发现更新您的问题,这样人们就不必查看 cmets 并可以帮助您
-
如果有一种方法可以在所有操作之前运行 espresso 命令,除非在 Activity 的第一个实例运行之后。我仍在寻找这个问题的答案。即 @BeforeClass 但在 Activity 运行之后。
标签: java android android-studio junit android-espresso