The Testing Pyramid: Fast Feedback, Low Cost
The Testing Pyramid guides test suite structure: a wide base of fast unit tests, a smaller middle of integration tests, and a tiny top of slow UI tests. This model is key for Android's local, instrumented, and UI tests. The footgun is inverting it.
Why it exists
Test suites with only end-to-end UI tests are slow, expensive to maintain, and flaky. A small change in the UI can break dozens of tests, slowing down development. The Testing Pyramid provides a strategy for getting fast, reliable feedback at a sustainable cost.
The mental model
Visualize a pyramid. The wide base is made of many small, fast, isolated unit tests. The middle layer has fewer, slightly larger integration tests that check how components work together. The narrow peak has a handful of slow, end-to-end UI tests that verify critical user flows. The higher you go up the pyramid, the slower, more expensive, and more brittle the tests become.
How it works
You structure your test suite according to the pyramid's layers. The base consists of local tests (Unit Tests) that run on the JVM without a device or emulator, testing individual classes or functions in isolation. The middle layer consists of instrumented tests (Integration Tests) that run on a device or emulator to verify interactions between a few components, like a Fragment and its ViewModel. The top layer consists of UI Tests that automate the user interface to test a complete user journey, like a full login flow. The goal is to push logic as far down the pyramid as possible to enable fast, cheap testing.
When to use it
Use this model when designing the testing strategy for any Android application. It provides a framework for deciding what kind of test to write for a given piece of functionality, balancing test coverage with execution speed and maintenance cost.
When not to use it
The pyramid is a guideline, not a rigid law. The main thing to avoid is the 'ice cream cone' anti-pattern, where the test suite is dominated by slow, flaky UI tests and has very few unit tests. This leads to a slow, unreliable build process that developers start to ignore.
One canonical example
For an Android login screen: write many unit tests for the ViewModel's validation logic (e.g., 'is email valid?'). Write a few integration tests to ensure the Fragment correctly calls the ViewModel. Write one end-to-end UI test that simulates a user typing and tapping the login button to verify the entire flow.
Interview question
According to the Testing Pyramid model, what is the primary negative outcome of having a test suite dominated by end-to-end UI tests?
- a.It leads to a slow, expensive, and unreliable build process.Correct
- b.It ensures that all bugs are caught only in production.
- c.It makes it impossible to test interactions between components.
- d.It prevents developers from writing any unit tests for new features.
Why? this is the answer
The card explicitly states that an 'ice cream cone' anti-pattern, dominated by UI tests, 'leads to a slow, unreliable build process that developers start to ignore.' While such a setup might lack unit tests, the primary consequence highlighted is the overall impact on development speed and reliability, not an absolute prevention of other test types or an impossibility of component interaction testing.
Just read this? Test yourself on what you have been reading.
Read the original → developer.android.com
- #android
- #testing
- #architecture
- #best-practices
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on android — each one lists the topics its interview covers.
See open roles