Stop 09 · Mobile TestingTopics · 8/8

Mobile Test Automation Frameworks

In short

Appium isn't the only option. Native frameworks like Espresso and XCUITest run faster and flake less, but you write tests twice. Knowing the trade-off is what makes you useful.

Beyond Appium — frameworks like Espresso (Android-native) and XCUITest (iOS-native) offer faster, platform-specific automation at the cost of cross-platform code reuse.

The purple blob in a doctor's coat stands between a large general medical bag and a slim specialist case.

Think of it like this

Family doctor vs specialist

Your family doctor handles almost anything, for the whole family. A heart specialist only does hearts, but does them faster and deeper. Appium is the family doctor for both platforms. Espresso and XCUITest are specialists, one per platform.

Watch it happen

The mobile framework family

Mobile UI tests

Cross-platform

Android native

iOS native

Appium

Detox (RN)

Espresso

XCUITest

1/5Every option automates taps and checks. They differ in where the test runs and who writes it.

The big ideas

What you need to know

Native is faster

Espresso waits for the app's main thread to go idle, so tests are quick and rarely flaky.

Cross-platform saves effort

One Appium suite can test both apps, as long as both expose similar ids.

Who writes them

Native frameworks sit inside the app project, so developers often write and run them too.

Mix and match

Many teams use native tests for quick component checks and Appium for full end-to-end flows.

See it in code

Walk through the code

kotlin

1@Test2fun loginShowsWelcomeMessage() {3    onView(withId(R.id.email))4        .perform(typeText("asha@test.com"), closeSoftKeyboard())5    onView(withId(R.id.password))6        .perform(typeText("Pass@123"), closeSoftKeyboard())7    onView(withId(R.id.login_button)).perform(click())8 9    onView(withText("Welcome, Asha")).check(matches(isDisplayed()))10}

1/3onView finds a view by its resource id. perform types and closes the keyboard.

An Espresso test in Kotlin. It lives in the app's androidTest folder and runs from Android Studio.

Save yourself the pain

Common mistakes

Oops

Choosing a native framework when QA has no access to the app's source code.

Do this instead

Espresso and XCUITest live inside the app project. Without source access, Appium is more practical.

Oops

Maintaining two full native suites for a small team.

Do this instead

Start with one cross-platform suite and add native tests only where speed matters.

Your mission

Peek at a native test

~35 min

Quick check

Your team has separate Android and iOS developers, and wants the fastest, least flaky UI tests. What fits best?

Go deeper

1Compare Appium's cross-platform approach to a native framework's platform-specific speed advantage.
2Learn why some teams choose native frameworks despite losing cross-platform code sharing.
3Understand the trade-off between automation speed and cross-platform maintainability.