【问题标题】:How to test an Intent in a none Activity class如何在无 Activity 类中测试 Intent
【发布时间】:2020-02-04 14:21:37
【问题描述】:

我正在尝试创建一个创建 Intent 并启动新 Activity 的类,现在我在测试它时遇到了问题。

private static final String TAG = IntentToActivity.class.getSimpleName();

// ----------------
// START VARIABLES
// ----------------
private String fqClassName;
private Intent intentToActivity;
private Context context;
// --------------
// END VARIABLES
// --------------

/**
 * Constructor sets needed variables, creates and performs intent
 * @param fqClassName full qualified class name to intent to
 * @param context context of the current using activity
 */
public IntentToActivity(String fqClassName, Context context) {
    this.fqClassName = fqClassName;
    this.context = context;

    performIntent();
}

/**
 * Creates and performs intent
 *
 * IMPORTANT: Intent must be referented in the manifest of the application use following code:
 * <intent-filter>
 *      <action android:name="com.example.exampleapplication.ExampleClass" />
 *      <category android:name="android.intent.category.DEFAULT" />
 * </intent-filter>
 */
private void performIntent() {
    if (fqClassName != null) {
        try {
            intentToActivity = new Intent(fqClassName);
            context.startActivity(intentToActivity);
        } catch (Exception e) {
            Log.e(TAG, "performIntent error: ", e);
        }
    }
}

}

我的安卓测试

公共类 IntentToActivityTest { @规则 public IntentsTestRule intentsRule = new IntentsTestRule(IntentToActivity.class);

@Test
public void newActivityLaunchingTest() {

    Intents.intended(IntentMatchers.hasComponent("com.example.mmal.example.auth.IntentToActity2Example"));

}

我的第一个问题,如何开始测试意图 我的第二个,如何实现一个非活动类作为规则

当前错误日志:

java.lang.RuntimeException: Could not launch activity
at androidx.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:467)
at androidx.test.rule.ActivityTestRule.launchActivity(ActivityTestRule.java:354)
at androidx.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:525)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
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 androidx.test.runner.AndroidJUnit4.run(AndroidJUnit4.java:104)
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 androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:388)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2108)
Caused by: java.lang.RuntimeException: Unable to resolve activity for: Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.motionminers.mmal.test/com.motionminers.mmal.backend.mv.IntentToActivity }
at android.app.Instrumentation.startActivitySync(Instrumentation.java:447)
at androidx.test.runner.MonitoringInstrumentation.access$101(MonitoringInstrumentation.java:98)
at androidx.test.runner.MonitoringInstrumentation$4.call(MonitoringInstrumentation.java:443)
at androidx.test.runner.MonitoringInstrumentation$4.call(MonitoringInstrumentation.java:440)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

【问题讨论】:

    标签: java android unit-testing android-intent android-espresso


    【解决方案1】:

    您不应测试 Android 类。这是因为模拟它,是一项非常繁重和艰苦的工作。

    在 MVP 架构中,您可以将 Intent 数据(例如 String)传递给 Presenter,这样他就可以分析这些数据并告诉 View(Activity)如何表现。

    因此,在这个示例场景中,您可以在构造函数中传递任何 String 数据并测试 Presenter 是否调用了某个 View 方法。

    【讨论】:

    • 所以你认为我应该对输入进行单元测试?不是意图?
    • 是的,如果 Intent 的数据中有布尔值,您将测试整个 Intent 功能吗?不,你只对布尔值感兴趣,所以你会玩这个布尔值。
    • 所以调用类并将 Intent 返回到单元测试以检查其是否为真......听起来很有趣。还是你的意思是别的?
    • 哦...不不,您的测试类不包含对 Android 类的任何引用。想象一下,你有一个 ExamplePresenter(boolean isLegacyModeEnabled),所以在你的测试类中可以创建一个测试方法来验证视图方法在什么时候调用该标志是 true 还是 false。在 Activity 实现中,您将拥有: ....presenter = new ExamplePresenter(Intent.getData(flag));
    • 你能解释得更具体一点吗?我需要如何测试这种情况?
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2020-06-15
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2021-11-09
    相关资源
    最近更新 更多