Android Instrumented testing asserting if an activity is started

Question

I am developing an Android application using Kotlin programming language. I am adding instrumentation tests into my application. Now I am trying to test if an activity is started after some delay.

This is my activity code.

class MainActivity : AppCompatActivity() {

    companion object {
        val LAUNCH_DELAY: Long = 2000
    }

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        Handler().postDelayed({
            this.startLoginActivity()
        }, LAUNCH_DELAY)
    }

    protected fun startLoginActivity()
    {
        startActivity(Intent(this, LoginActivity::class.java))
    }
}

I know how to write a simple test like this

@Test
fun itRendersCompanyName() {
    onView(withId(R.id.main_tv_company_name)).check(matches(withText("App Name")))
}

But what I am trying to test here is if the LoginActivity is launched after some delay. How can I do it using Espresso framework?

Saeed Masoumi · Answer 1 · 2019-09-22T12:19:22.923

You can get the visible Activity using ActivityManager:

inline fun <reified T : Activity> isVisible(): Boolean {
    val am = ApplicationProvider.getApplicationContext<Context>().getSystemService(ACTIVITY_SERVICE)
            as ActivityManager

    val visibleActivityName = if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.M) {
        am.appTasks[0].taskInfo.topActivity.className
    } else {
        am.getRunningTasks(1)[0].topActivity.className
    }
    return visibleActivityName == T::class.java.name
}

Calling isVisible<LoginActivity>() will tell you that LoginActivity is visible or not.

Also, to wait until your LoginActivity visible, you can wait for this method to gets true. For example:

inline fun <reified T : Activity> waitUntilActivityVisible() {
    val startTime = System.currentTimeMillis()
    while (!isVisible<T>()) {
        Thread.sleep(200)
        if (System.currentTimeMillis() - startTime >= TIMEOUT) {
            throw AssertionError("Condition unsatisfied after $TIMEOUT milliseconds")
        }
    }
}

I recommend checking for null in appTasks getter: val visibleActivityName = am.appTasks.elementAtOrNull(0)?.taskInfo?.baseActivity?.className — tonisives, Oct 09 '20 at 03:14

Natig Babayev · Accepted Answer · 2019-09-22T12:49:01.997

1

You can use Intents.intended() for that.

Add following to your build.gradle file:

androidTestImplementation 'androidx.test.espresso:espresso-intents:3.1.0'

In your test function, you can try following code:

Intents.init()
Intents.intended(hasComponent(LoginActivity::class.java!!.getName()))

You can read more about Espresso-Intents here.

edited Sep 22 '19 at 12:49

answered Sep 22 '19 at 11:58

Natig Babayev

3,128
15
23

Hi Natig, there are three different Intents in my project. Which one do I have to use. None of them has intented method in it. – Wai Yan Hein Sep 22 '19 at 12:01
Would you be able to specify the full class name or namespace, please? – Wai Yan Hein Sep 22 '19 at 12:01
You have to add `androidTestImplementation 'androidx.test.espresso:espresso-intents:3.1.0'` to your app level build.gradle file. – Natig Babayev Sep 22 '19 at 12:02
This is class name with package name: `androidx.test.espresso.intent.Intents` – Natig Babayev Sep 22 '19 at 12:03
Don't forget to add Thread.sleep(2000) before calling intended() function as your action will be executed after 2 seconds according to your code. – Natig Babayev Sep 22 '19 at 12:06
Thanks for the answer. But I got another issue. Please, https://stackoverflow.com/questions/58049150/android-kotlin-expresso-asserting-intended-activity-in-the-unit-test-is-throwing – Wai Yan Hein Sep 22 '19 at 12:20
Have you tried adding Thread.sleep(2000) before calling Intents.intended() ? – Natig Babayev Sep 22 '19 at 12:21
Hi that is completely different issue. I removed the delay. – Wai Yan Hein Sep 22 '19 at 12:22
Oh, ok. I'll check. – Natig Babayev Sep 22 '19 at 12:23
To get null pointer exception, you can put Intents.init() before Intents.intended. – Natig Babayev Sep 22 '19 at 12:48
Would you be able to post the answer on the other question please? – Wai Yan Hein Sep 22 '19 at 12:49
I also updated the question because I got another issue after I use init() – Wai Yan Hein Sep 22 '19 at 12:51
I used your answer, I got anther issue. – Wai Yan Hein Sep 22 '19 at 12:52
Ok. I’ll check that as well. – Natig Babayev Sep 22 '19 at 12:52
I added fix in that new question – Natig Babayev Sep 22 '19 at 13:25

score 1 · Answer 3 · answered Sep 22 '19 at 12:01

1

It’s better to test this state with unit tests. Use architecture pattern (for example MVP/MVVM), mock presenter/view model and check what method which is responsible for activity start is triggered

answered Sep 22 '19 at 12:01

Peter Staranchuk

1,343
3
14
29

1

How to test if a method is triggered in android? – Wai Yan Hein Sep 22 '19 at 12:41
1

Mockito.verify(mockedClass).someMethod(parameters) – Peter Staranchuk Sep 23 '19 at 07:14
for example: in @Before: presenter = Mockito.spy(SomePresenter(...)) in test: Mockito.verify(presenter, times(1)).startLoginActivity() where times(1) mean what is was exactly one interaction – Peter Staranchuk Sep 23 '19 at 07:15

score 0 · Answer 4 · answered Dec 01 '22 at 03:30

I got it working using the following:

val expectedUrl = "https://yoururlhere"    
Intents.init();
Matcher<Intent> expectedIntent = allOf(hasAction(Intent.ACTION_VIEW), hasData(expectedUrl));
intending(expectedIntent).respondWith(new Instrumentation.ActivityResult(0, null));
onView(withId(R.id.someViewId)).perform(click());
intended(expectedIntent);
Intents.release();

And remember to add "androidTestImplementation 'androidx.test.espresso:espresso-intents:3.1.0'" to your gradle dependency

Android Instrumented testing asserting if an activity is started

4 Answers4