Sample project of Android GUI test automation using Espresso, Cucumber and the Page Object Pattern
Alternatives To Cleanguitestarchitecture
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Green Coffee218
2 years ago1mitJava
Android library that allows you to run your acceptance tests written in Gherkin in your Android instrumentation tests.
6 years ago5mitJava
Sample project of Android GUI test automation using Espresso, Cucumber and the Page Object Pattern
5 years agomitJava
A sample project for Cucumber and Espresso in Android
3 years ago2apache-2.0Java
Android project to experiment various testing tools
Espresso Cucumber47
8 years ago1apache-2.0Java
Library to test Android applications using Espresso test framework with cucumber BDD language and Spoon screenshots
4 years ago3apache-2.0Java
Android BDD Espresso + Cucumber
Android Cucumber Espresso12
7 years agoJava
A template project to demonstrate the usage of Cucumber along with Espresso for acceptance testing on Android.
7 years agoJava
Workshop Android Espresso with Cucumber jvm
No Cucumber1
5 years agoKotlin
A toolset for making your manager happy and staying sane at the same time
Alternatives To Cleanguitestarchitecture
Select To Compare

Alternative Project Comparisons

Build Status

Clean GUI Test Architecture

Sample project of Android GUI test automation using Espresso, Cucumber and the Page Object Pattern

The evolution journey of Android GUI testing

The code in this repository serves as a support example of all the test solutions discussed in this published article:

Execute the project

Open the project in Android Studio and select the gradle task 'connectedCheck'

Alternative, from the command line run gradlew connectedCheck

Cucumber supports filtering execution of test scenarios with tags (i.e. @login-scenarios). To filter by tags you have the following options (which can't be combined):

  • Hard coded tags in annotation @CucumberOptions inside
  • Use parameters in command line like ./gradlew connectedAndroidTest -Ptags="@login-scenarios,@kitkat"
  • In Android Studio, run connectedAndroidTest in the right Gradle tab and then edit the run configuration to add under the Script parameters something like -Ptags="@login-scenarios,@kitkat"

More information about how to use and combine Cucumber tags here.

Note: Make sure to connect a phone to the computer or start an emulator before running the tests.

In a nutshell

The sample test code can be summarized in these three elements:

1- Feature file describing the test scenario in English:

@ScenarioId("MyApp-135") @login-scenarios
Scenario: User can login with valid user name and password
    Given I see the login page
    When I login with user name "Sebas" and password "passion"
    Then I see the welcome page
    And the title is "Welcome Sebas"

2- Java glue code to translate English to Java (this is a step definition):

@Given("^I see the login page$")
public void i_see_the_login_page() {
    mCurrentPage = new LoginPage();

@When("^I login with user name \"(.+)\" and password \"(.+)\"$")
public void i_login_with_username_and_password(final String userName, final String password) {
    mCurrentPage =, password);

@Then("^I see the welcome page$")
public void i_see_the_welcome_page() {;

@And("^the title is \"(.+)\"$")
public void the_title_is(final String title) {;

3- Page Object class implementing the interactions between tests and tested application:

 * Perform the login and return the next Welcome page/view
 * @param userName Name of the user to login
 * @param password Password of the user to login
 * @return Welcome page/view
public WelcomePage doLogin(String userName, String password) {
    onView(withId(, closeSoftKeyboard());
    return new WelcomePage();

Advanced scenarios

When the code of your application and tests mature enough you will be doing things like this:

  • A test step from a test scenario that can be reused across multiple tests:
    Given I login into premium account
  • The step definition describes a lot of steps that need to happen to perform the requested action:
@Given("^I login into premium account$")
public void i_log_in_to_premium() {
    mCurrentPage = mCurrentPage

This step definition still hides most of the implementation details inside the Page Objects that contain the actual how-to communicate with the tested application.


This content is released under the MIT License:

Popular Cucumber Projects
Popular Espresso Projects
Popular Software Quality Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Test Automation