Skip to content

Most visited

Recently visited


Espresso Web

Espresso-Web is an entry point to work with Android WebView UI components. Espresso-Web reuses Atoms from the popular WebDriver API to examine and control the behavior of a WebView.

When to use Espresso-Web

Use Espresso-Web to test your hybrid apps, especially the integration of your app’s native UI components with its WebView UI components. You can use the Espresso-Web API in conjunction with other Espresso APIs to fully interact with web elements inside WebView objects.

If you need to test only the WebView itself, and not the interactions between the WebView and native components in your app, consider writing a general web test using a framework like WebDriver. If you use a web testing framework, you don’t need to use an Android device or a Java Virtual Machine, which makes your tests run more quickly and reliably. That being said, Espresso-Web allows you to reuse your custom WebDriver atoms, which gives you a lot of flexibility, especially when writing tests that you plan to run against both standalone web apps and apps that include an Android UI.

How it works

Similarly to Espresso’s onData() method, a WebView interaction comprises several Atoms. WebView interactions use a combination of the Java programming language and a JavaScript bridge to do their work. Because there is no chance of introducing race conditions by exposing data from the JavaScript environment—everything Espresso sees on the Java-based side is an isolated copy—returning data from Web.WebInteraction objects is fully supported, allowing you to verify all data that’s returned from a request.

What is a WebDriver Atom?

The WebDriver framework uses Atoms to find and manipulate web elements programmatically. Atoms are used by WebDriver to allow browser manipulation. An Atom is conceptually similar to a ViewAction, a self-contained unit that performs an action in your UI. You expose Atoms using a list of defined methods, such as findElement() and getElement(), to drive the browser from the user’s point of view. However, if you use the WebDriver framework directly, Atoms need to be properly orchestrated, requiring logic that is quite verbose.

Within Espresso, the classes Web and Web.WebInteraction wrap this boilerplate and give an Espresso-like feel to interacting with WebView objects. So in a context of a WebView, Atoms are used as a substitution to traditional Espresso ViewMatchers and ViewActions.

The API then looks quite simple:


To learn more, read Selenium’s documentation on Atoms.

Implementing WebView


To include Espresso-Web in your project, complete the following steps:

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

    androidTestCompile ''
  3. Espresso-Web is only compatible with Espresso 2.2 or higher and the Android Testing Support Library 0.3 or higher, so make sure you update those lines as well:

    androidTestCompile ''
    androidTestCompile ''
    androidTestCompile ''

Common API usage

The onWebView() method is the main entry point when working with WebView on Android using Espresso. You use this method to perform Espresso-Web tests, such as the following:

    .withElement(findElement(Locator.ID, "link_2")) // similar to onView(withId(...))
    .perform(webClick()) // Similar to perform(click())

    // Similar to check(matches(...))
    .check(webMatches(getCurrentUrl(), containsString("navigation_2.html")));

In this example, Espresso-Web locates a DOM element whose ID is "link_2" and clicks on it. The tool then verifies that the WebView sends a GET request containing the "navigation_2.html" string.

Note: When executing your tests, the system performs all WebView interactions using JavaScript. Therefore, to support JavaScript evaluation, the WebView under test must have JavaScript enabled.

You can force JavaScript to be enabled by overriding afterActivityLaunched() in the ActivityTestRule and calling onWebView().forceJavascriptEnabled(). Enabling JavaScript may cause the WebView under test to be reloaded. This is necessary to ensure that AndroidJUnitRunner loads all needed test infrastructure, including JavaScript interactions:

public ActivityTestRule mActivityRule =
        new ActivityTestRule(WebViewActivity.class,
        false, false) {
    protected void afterActivityLaunched() {

Common web interactions

Common interactions with Web.WebInteraction objects include the following:


The following example tests whether, after entering text into a WebView and selecting a Submit button, the same text appears within a different element in the same WebView:

public static final String MACCHIATO = "Macchiato";

public void typeTextInInput_clickButton_SubmitsForm() {
    // Lazily launch the Activity with a custom start Intent per test.

    // Selects the WebView in your layout. If you have multiple WebView objects,
    // you can also use a matcher to select a given WebView,
    // onWebView(withId(
        // Find the input element by ID.
        .withElement(findElement(Locator.ID, "text_input"))

        // Clear previous input and enter new text into the input element.

        // Find the "Submit" button and simulate a click using JavaScript.
        .withElement(findElement(Locator.ID, "submitBtn"))

        // Find the response element by ID, and verify that it contains the
        // entered text.
        .withElement(findElement(Locator.ID, "response"))
        .check(webMatches(getText(), containsString(MACCHIATO)));

See also the Espresso Web sample on GitHub.

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


Sigue a Google Developers en WeChat

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 short survey?
Help us improve the Android developer experience. (Dec 2017 Android Platform & Tools Survey)