Automate Android Apps With UI Automator

UI Automator is an Android testing framework that allows you to automate UI testing of Android apps. It enables interaction with UI elements, sending input events, and verifying mobile app behaviors on emulators or real devices.

What Is UI Automator?

UI Automator is a framework for automating user interactions on mobile apps and system UI components on Android devices, such as launching the settings menu or interacting with the app launcher.

You can also locate UI components using intuitive attributes like visible text or content descriptions, without relying on internal implementation details of the mobile app.

UI Automator is based on instrumentation APIs and works with the AndroidJUnitRunner test runner. So, it is suitable for black-box testing scenarios where tests simulate user behavior without accessing the app’s codebase.

Prerequisites

Before writing your first Android UI Automator test for Android app testing, ensure you meet the following prerequisites:

1. Install Android Studio and make sure the Android SDK tools are downloaded during setup.
2. Install Java Development Kit (JDK) v8 or above.
3. Set up an emulator (or real device) running Android 4.3 (API level 18) or above for testing.
4. Add Android Debug Bridge (ADB) to your system path so you can run ADB commands from the terminal.
5. Enable and use Layout Inspector in Android Studio to inspect UI elements and identify reliable selectors.

Note

Test your mobile apps on real Android devices. Try LambdaTest Today!

Add UI Automator Dependencies

Here we’ll use an Android emulator to execute tests. Once you have set up the Android emulator, let’s add the UI Automator dependencies:

1. Create an Android testing project.
2. To use UI Automator, add dependencies for uiautomator and junit in the app/build.gradle file.
dependencies { ... androidTestImplementation ‘androidx.test.ext:junit:1.2.1’ androidTestImplementation ‘androidx.test:runner:1.2.0’ androidTestImplementation ‘androidx.test.uiautomator:uiautomator:2.3.0’ }

1 2 3 4 5 6

dependencies {   ... androidTestImplementation ‘androidx.test.ext:junit:1.2.1’ androidTestImplementation ‘androidx.test:runner:1.2.0’ androidTestImplementation ‘androidx.test.uiautomator:uiautomator:2.3.0’ }

3. After adding these dependencies, sync the Gradle project.

Write Tests With UI Automator

Let’s write a test to open the proverbial app and verify the button functionality.

Test Scenario:

Once your Android emulator is up, run the adb install <path-to-LambdaTest-proverbial-apk-file> command to install the LambdaTest proverbial app.

Implementation:

1. Create a setup method with the @Before annotation.

For this use case, we will initialize the UiDevice instance and press the Home button to ensure the test starts from the home screen.

@Before public void setup() { device = UiDevice.getInstance(InstrumentationRegistry.getInstrumentation()); device.pressHome(); }

1 2 3 4 5

@Before public void setup() {     device = UiDevice.getInstance(InstrumentationRegistry.getInstrumentation());     device.pressHome(); }



This setup will also include the launch of the proverbial app with the ADB command.

//start Proverbial app with adb command device.executeShellCommand("am start -n com.lambdatest.proverbial/.MainActivity”); // Validate that activity has been opened. Assert.assertTrue(device.hasObject(By.pkg(“com.lambdatest.proverbial”)));

1 2 3 4

//start Proverbial app with adb command device.executeShellCommand("am start -n com.lambdatest.proverbial/.MainActivity”); // Validate that activity has been opened. Assert.assertTrue(device.hasObject(By.pkg(“com.lambdatest.proverbial”)));

2. Use Layout Inspector to inspect and identify selectors/locators. Then, use the resource ID to uniquely identify the welcome message on the home page of the mobile app.
3. Locate the text label element and verify its initial content.
// initialize the text label element UiObject2 textElement = device.findObject(By.res(“<replace_with_package_name_of_app>”, "Textbox")); // Assert the initial text Assert.assertEquals("Hello! Welcome to lambdatest Sample App called Proverbial", textElement.getText());

1 2 3 4

// initialize the text label element UiObject2 textElement = device.findObject(By.res(“<replace_with_package_name_of_app>”, "Textbox")); // Assert the initial text Assert.assertEquals("Hello! Welcome to lambdatest Sample App called Proverbial", textElement.getText());

4. Simulate a user clicking the button that updates the text.
UiObject2 textButton = device.findObject(By.res(PACKAGE_NAME, "Text")); //Click on Text button to update the element textButton.click();

1 2 3

UiObject2 textButton = device.findObject(By.res(PACKAGE_NAME, "Text")); //Click on Text button to update the element textButton.click();

5. Check if the text element updates as expected.

Run the Android UI Automator Tests

From the Android Studio, click Run ‘ProverbialTest’ to execute the tests:

You can notice that your test is executed and passed.

If you want to run Android automated tests at scale, you can leverage a cloud-based testing platform like LambdaTest. It is a GenAI-native test execution platform that offers a scalable real device cloud to run automated tests on real Android devices without the need for physical infrastructure.

With LambdaTest, you can test across a wide range of Android and iOS devices, covering multiple OS versions and device brands like iPhone, Samsung, Google Pixel, etc. It also supports automation using popular frameworks like Appium, Espresso, and XCUITest, enabling faster, more reliable mobile app testing at scale.

Key APIs of UI Automator

Let’s understand the key APIs of UI Automator that help interact with Android apps and their UI components, allowing automation of clicks, text input, scrolling, and more.

• JUnitTestRunner: Initializes and runs Android UI Automator tests, coordinating the execution flow of your test class.
• UiDevice: Represents the full Android device interface, allowing control over hardware buttons and system-level actions.
• BySelector: Defines criteria to locate UI elements using properties like text, class name, or resource ID.
• findObject(): Searches for a UI element in the device’s current UI hierarchy that matches the specified BySelector criteria.
• UiObject2: Represents a UI element and allows interactions like clicks, swipes, typing, and reading attributes.
• AccessibilityService: Reads and controls UI elements using the Android Accessibility API, often for enhanced automation or accessibility tools.
• AndroidUI Framework: Displays and manages the visible UI elements on the screen, bridging between the app’s layout and the system.

Best Practices for Writing Stable UI Automator Tests

To write Android UI Automator tests that are both stable and maintainable, you can consider the following best practices:

• Always Start From a Clean State: Before each test, reset your app or device to a known screen, like the home screen, using the device.pressHome() method.

If a test modifies settings or login state, make sure to clean that up afterward using @After methods. This keeps tests independent and repeatable.

• Use Reliable Selectors: When identifying UI elements, go for stable attributes like resource ID or content description using methods like By.res() or By.desc().

Avoid relying on visible text, as it can change or get localized, making your tests flaky. If you’re building the app, add android:contentDescription to key elements to make them both testable and accessible.

• Don’t Hard Code Waits: Avoid using the Thread.sleep() method. Instead, wait for elements or conditions dynamically using device.wait(Until.hasObject(…)). This makes your tests faster and more reliable across devices with different performance.
• Use Setup and Teardown Hooks: Structure your test classes with @Before to handle initial setup like launching the app or logging in, and @After to clean things up. This reduces repeated code and keeps tests consistent.
• Account for Device Differences: Android devices vary in screen sizes, OS versions, and themes, so your selectors should be flexible. Use methods like By.textStartsWith() or By.descContains() when the exact text isn’t ensured.

Also, use @SdkSuppress to skip tests that aren’t applicable on certain Android versions.

• Use Clear Names and Logs: Always use meaningful test method names like testLogin_showsErrorOnInvalidPassword() so others (or your future self) can quickly understand what the test does. Logging with the Log.d() method can also be really helpful when debugging issues, especially in CI pipelines.
• Reduce Randomness and External Dependencies: Network delays, real-time data, and third-party dependencies can cause flaky tests. Stub responses if you can, or use test environments. If unpredictability is unavoidable, add retry logic or longer timeouts to handle it.

Conclusion

If you’ve made it this far, you now have a solid foundation for using UI Automator to automate Android app testing, from setup and writing tests to understanding key APIs.

UI Automator is great for functional UI testing. However, running Android tests across many devices and OS versions can be complex and time-consuming. That’s where a platform like LambdaTest becomes helpful. It lets you instantly run automated tests on real Android devices in the cloud, no physical labs or maintenance needed.

Citations

• Write automated tests with UI Automator: https://developer.android.com/training/testing/other-components/ui-automator
• AndroidJUnitRunner: https://developer.android.com/training/testing/instrumented-tests/androidx-test-libraries/runner
• Debug your layout with Layout Inspector: https://developer.android.com/studio/debug/layout-inspector

Yogendra Porwal

Yogendra is a Test Automation Solution Architect with 10+ years of experience across web, mobile, and API testing. Skilled in Java, JavaScript, and Python, he has hands-on expertise with tools like Rest Assured, pytest, Locust, and JMeter. He specializes in continuous testing, shift-left practices, and performance testing in Agile environments.

See author's profile