Skip to content

Most visited

Recently visited


Espresso intents

Espresso-Intents is an extension to Espresso, which enables validation and stubbing of Intents sent out by the application under test. It’s like Mockito, but for Android Intents.


Open your app’s build.gradle file. This is usually not the top-level build.gradle file but app/build.gradle. Add the following line inside dependencies:

androidTestCompile ''

Espresso-Intents is only compatible with Espresso 2.1+ and the testing support library 0.3+ so make sure you update those lines as well:

androidTestCompile ''
androidTestCompile ''
androidTestCompile ''

Test rules

Use IntentsTestRule instead of ActivityTestRule when using Espresso-Intents. IntentsTestRule makes it easy to use Espresso-Intents APIs in functional UI tests. This class is an extension of ActivityTestRule, which initializes Espresso-Intents before each test annotated with @Test and releases Espresso-Intents after each test run. The activity will be terminated after each test and this rule can be used in the same way as ActivityTestRule.


Espresso-Intents records all intents that attempt to launch activities from the application under test. Using the intended API, closely related to Mockito.verify(), you can assert that a given intent has been seen.

An example test that simply validates an outgoing intent:

public void validateIntentSentToPackage() {
    // User action that results in an external "phone" activity being launched.

    // Using a canned RecordedIntentMatcher to validate that an intent resolving
    // to the "phone" activity has been sent.


Using the intending API, closely related to Mockito.when(), you can provide a response for activities that are launched with startActivityForResult(). This is particularly useful for external activities since we cannot manipulate the user interface of an external activity nor control the ActivityResult returned to the activity under test.

The following code snippet contains an example test with intent stubbing:

public void activityResult_IsHandledProperly() {
    // Build a result to return when a particular activity is launched.
    Intent resultData = new Intent();
    String phoneNumber = "123-345-6789";
    resultData.putExtra("phone", phoneNumber);
    ActivityResult result = new ActivityResult(Activity.RESULT_OK, resultData);

    // Set up result stubbing when an intent sent to "contacts" is seen.

    // User action that results in "contacts" activity being launched.
    // Launching activity expects phoneNumber to be returned and displays it
    // on the screen.

    // Assert that data we set up above is shown.


The intending() and intended() methods take a hamcrest Matcher<Intent> object as an argument. Hamcrest is a library of matcher objects, also known as constraints or predicates). You have the following options for using them:

An example of intent validation with existing Intent matchers:

        hasEntry(equalTo("key1"), equalTo("value1")),
        hasEntry(equalTo("key2"), equalTo("value2")))),
This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a one-minute survey?
Help us improve Android tools and documentation.