Android Test Pyramid: Keep Device Tests Focused
Running every check on an emulator makes feedback slow. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Put pure logic in fast local tests and reserve device tests for framework and interaction behavior.
- Choose a few end-to-end flows for login, storage and permissions.
What to check
A mock-heavy local test may miss wiring mistakes; keep a small number of real integration checks. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.