Develop Reference

Using ActivityTestRule for multiple activities in an Espresso Test

I have a test that I want to get working in espresso to fetch all (100+) Activities in my app and assert that they start an Intent to launch a dialog activity. The test works perfecting on the first activity in the list (or if there is just one activity), but fails on the second activity, because espresso tries to cast it to the first activity.
I have to use ActivityTestRule and not launch the activity directly from the context, or Intendo intended assertions don't work.
Most of the documentation shows espresso being setup with one activity per test, which is not possible in my case, because I'm loading the list of activities dynamically.
Espresso is saving some kind of internal state that I can't figure out how to clear. Does anyone know how to clear it between assertions in a for loop?
Or is there another class other than ActivityTestRule without the internal state that also works with intended?
Here is an example of what I'm trying to test:
ActivityInfo[] activities =
appContext
.getPackageManager()
.getPackageInfo(appContext.getPackageName(), PackageManager.GET_ACTIVITIES)
.activities;
for (ActivityInfo activityInfo : activities) {
String className = activityInfo.name;
ActivityTestRule activityTestRule =
new ActivityTestRule<>((Class<Activity>) Class.forName(className));
Intent intent = new Intent()
.setClassName(appContext, className)
.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
activityActivityTestRule.launchActivity(intent);
intended(hasComponent(ExpectedDialogActivity.class.getName()));
activityActivityTestRule.finishActivity();
}

Clear Intents between instrumentation tests

One of my Espresso tests is apparently failing because a broadcast intent triggered by the previous test is arriving part way through the subsequent test. At this point, the application is in an inconsistent state and missing some SharedPreferences which are expected by the intent handler.
Is there a way to make sure that all waiting intents have been processed or cancelled before starting an Espresso test?

I don't think there is a way to clear intents that are already dispatched. However you can get around this by tweaking your "previous test".
If you want to fully take advantage of Espresso you have to reduce the scope of your test as small as possible. So instead of broadcasting an intent and verifying what happens next, try stubbing your intents.
Use IntentsTestRule instead of ActivityTestRule and stub out all internal intents (sometimes even the external ones) using the below code:
intending(isInternal()).respondWith(new Instrumentation.ActivityResult(Activity.RESULT_OK, null));
Now in your "previous test", check if the right intent is getting broadcasted using something like:
intended(hasComponent("com.example.something.SomeActivity"));
This way, you can test your functionality without actually broadcasting any intents. I always stub my Internal and External intents and verify if the right intent is getting triggered in all my tests. This way the next activity doesn't get launched and my Espresso tests are faster and stable. Always ensure to test only what you are want to test, and keep the scope really small.
Read more: https://google.github.io/android-testing-support-library/docs/espresso/intents/

I had the same problem testing two intents,
one to share text and another to share audio.
I managed to do it by calling between the intents.
Intents.init()
//
Intents.release()
I don't know if it is the right way but is working on the question.
Let say I have to check two Intents with action CHOOSER.
Even my intents are ACTION_SEND, I have a CHOOSER in my code to send intent.
Intents.init()
testIntent1
Intents.release()
Intents.init()
testIntent2
Intents.release()
testIntent1() {
Matcher<Intent> expectedIntent = getIntentMatcherChooser();
String textInET = "share this text";
replaceTextCloseKeyboard(R.id.et_main, text);
openDrawerClickItem(R.id.nav_item_share_text);
intended(expectedIntent);
}
getIntentMatcherChooser(){
Matcher<Intent> expectedIntent = allOf(hasAction(Intent.ACTION_CHOOSER));
intending(expectedIntent).respondWith(new Instrumentation.ActivityResult(0, null));
}

How can I check the expected intent sent without actually launching activity in Espresso?

I have a UI test which clicks a button, and then launch a new Activity in its onClickListener. The test checks whether expected intent is sent or not.
My problem is, I want to test whether expected intent is sent without actually launching the activity. Because I found that new activity initializes its state, and it makes subsequent tests flaky.
I know there are two Espresso Intents API, which are intended and intending, but both fail to meet my needs. intended API actually launches the target activity, and intending API doesn't launch the activity, but it calls onActivityResult callback which I don't want either. Because I'm afraid that code inside onActivityResult may cause another flakiness.
Also intending doesn't assert whether matching intent is sent. It just calls onActivityResult callback when matching intent is found, which means I have to check whether onActivityResult is called or not!
Is there a clean way to achieve what I want?

If you want to test whether expected intent is sent without actually launching the activity you can do it by capturing the intent with an activityResult and then catching the activity :
Intent intent = new Intent();
ActivityResult intentResult = new ActivityResult(Activity.RESULT_OK,intent);
intending(anyIntent()).respondWith(intentResult);
onView(withId(R.id.view_id_to_perform_clicking)).check(matches(isDisplayed())).perform(click());
intended(allOf(hasComponent(ActivityToBeOpened.class.getName())));
This would catch any attempt of launching ActivityToBeOpened. If you want to be more specific you can also catch an intent with Extras:
intended(allOf(hasComponent(ActivityToBeOpened.class.getName()), hasExtra("paramName", "value")));
Hope that helps.

Espresso's Intents class is a concise and handy api, but when it doesn't meet your needs, there is an alternative. If you use AndroidJUnit4 test runner, you can get Instrumentaion instance using InstrumentationRegistry.getInstrumentation(), and then you can add Instrumentation.ActivityMonitor instance.
Instrumentation.ActivityMonitor am = new Instrumentation.ActivityMonitor("YOUR_ACTIVITY", null, true);
InstrumentationRegistry.getInstrumentation().addMonitor(am);
onView(withId(R.id.view_id_to_perform_clicking)).check(matches(isDisplayed())).perform(click());
assertTrue(InstrumentationRegistry.getInstrumentation().checkMonitorHit(am, 1));
The third parameter of ActivityMonitor constructor tells we want to block activity launching. Note that this approach has its limitation. In contrast to Espresso Intents' rich Matcher support, You can not set multiple condition for ActivityMonitor.
You can find several samples in ApiDemos, especially in ContactsSelectInstrumentation class.

Actually, you can block any intent to launch an external or your own activity but still use the rich Espresso Intents API:
Instrumentation.ActivityMonitor soloMonitor = solo.getActivityMonitor();
instrumentation.removeMonitor(soloMonitor);
IntentFilter filter = null;
// Block any intent
Instrumentation.ActivityMonitor monitor = instrumentation.addMonitor(filter, null, true);
instrumentation.addMonitor(soloMonitor);
// User action that results in an external browser activity being launched.
user.clickOnView(system.getView(R.id.callButton));
instrumentation.waitForIdleSync();
Intents.intended(Matchers.allOf(
IntentMatchers.hasAction(Matchers.equalTo(Intent.ACTION_VIEW)),
IntentMatchers.hasData(Matchers.equalTo(Uri.parse(url))),
IntentMatchers.toPackage(chromePackage)));
instrumentation.removeMonitor(monitor);
You able to do that because Espresso Intents still records every Intent with IntentMonitor callback even if you block them. Look at the source code of Espresso Intents on how they do that.
If you use Robotium Solo framework you need to move your own ActivityMonitor before their one. Otherwise just skip the lines related to this.

Espresso : test startActivityForResult return RESULT_OK

I got an Android app that requires authentication to be used. As the project grows up, I want to add unit testing in my app.
To do that, I use Espresso 2.1
The thing is:
My LoginActivity is called by startActivityForResult
It shows the form
a. If the credentials are wrong, it stays on the LoginActivity
b. If the credentials are ok, it finish with a RESULT_OK.
So in my espresso test class, I have some unit tests. Everything is fine with the not ok cases, the problem is on the ok case.
I need to check that the result is RESULT_OK but as the Activity finishes, espresso failed with a
android.support.test.espresso.NoActivityResumedException: No activities in stage RESUMED. Did you forget to launch the activity. (test.getActivity() or similar)?
Here is my questions:
Is there a way to test the setResult of the Activity ?
Is there a workaround (I'd like to not use any of them, but at least...) to be able to test that ?
I've read things about Espresso-Intents but I can't figure out an example on how I can start an activity of my own package and check the result is a RESULT_OK.

Very short answer:
yes, it is possible to set the result by doing
Intent resultData = new Intent();
resultData.setData(...);
Instrumentation.ActivityResult result = new Instrumentation.ActivityResult(Activity.RESULT_OK, resultData);
intending(toPackage("package.containing.login.activity")).respondWith(result);
You would asses that the RESULT_OK was received by checking that one of the views contains the desired returned information.
If that is not clear enough, post any questions in the comments and will try to help.
how I can start an activity of my own package
How would the user do it? Probably by clicking on a button or any other view interaction, right?

Do you really need Espresso for this test? Robolectric ActivityShadow has getResultCode() and getResultIntent() methods.
final Intent startIntent = new Intent();
final ResultActivity activity = Robolectric.buildActivity(ResultActivity.class)
.withIntent(startIntent)
.create()
.get();
final String data = "data";
activity.onEventMainThread(new CompletedEvent(data));
assertEquals(RESULT_OK, shadowOf(activity).getResultCode());
final Intent resultIntent = shadowOf(activity).getResultIntent();
assertEquals(data, resultIntent.getStringExtra(DATA_KEY));
ResultActivity sets result and finishes after receiving a CompletedEvent. In this test the event handler is called directly to simulate the event.

Controlling Application during testing android

I using Roboguice to test application. I have two Modules for the app:
ProductionModule - used when application is not under test
TestingModule - used when application is under test
Those Modules are parameters for Injector which created in OnCreate() method of APPLICATION.
So how can i figure out, if the app is under test?
Is there a way to manage an APPLICATION lifecycle in ActivityInstrumentationTestCase2, so i can do some stuff BEFORE APPLICATION onCreate() method?
PS: I need to test activities after that so i using ActivityInstrumentationTestCase2 and i using custom TestRunner to generate reports.

Application on create is called before any of your tests run, this is because to run tests your application already has to exist.
You can however call application oncreate yourself within a test. You can cast an applicationcontext to your application and then call the onCreate method. I have had to do this in the past in order to clear any state in the application.

You can send extra params to the activity from JUnit in the setUp() like this:
#Override
public void setUp() {
Intent intent = new Intent();
intent.putExtra("debug", true);
setActivityIntent(intent);
mActivity = getActivity();
}
And inside the real Activity you can check it like this inside onCreate():
Bundle extras = getIntent().getExtras();
if(extras!=null){
boolean is= (Boolean)extras.get("debug");
if(is){
// here you are in debug mode
}
}