Stay organized with collections
Save and categorize content based on your preferences.
Testing your app is an integral part of the app development process. By running
tests against your app consistently, you can verify your app's correctness,
functional behavior, and usability before you release it publicly.
Testing also offers the following advantages:
- Rapid feedback on failures.
- Early failure detection in the development cycle.
- Safer code refactoring, allowing you to optimize code without worrying
about regressions.
- Stable development velocity, helping you minimize technical debt.
Documentation
The documentation covers best practices around testing Android apps:
Additional resources
For more information about testing on Android, consult the following resources.
Samples
Codelabs
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-02-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-10 UTC."],[],[],null,["# Test apps on Android\nPart of [Android Jetpack](/jetpack).\n=========================================================\n\nTesting your app is an integral part of the app development process. By running\ntests against your app consistently, you can verify your app's correctness,\nfunctional behavior, and usability before you release it publicly.\n\nTesting also offers the following advantages:\n\n- **Rapid feedback** on failures.\n- **Early failure detection** in the development cycle.\n- **Safer code refactoring**, allowing you to optimize code without worrying about regressions.\n- **Stable development velocity**, helping you minimize technical debt.\n\nDocumentation\n-------------\n\nThe documentation covers best practices around testing Android apps:\n\n- [Fundamentals of testing Android apps](/training/testing/fundamentals)\n- [Build local unit tests](/training/testing/local-tests) that run on the host\n- [Build instrumented tests](/training/testing/instrumented-tests) that run on devices or emulators\n- Verify UIs with [Behavior](/training/testing/ui-tests/behavior) and [Screenshot tests](/training/testing/ui-tests/screenshot)\n- [Test different screen sizes](/training/testing/different-screens)\n\nAdditional resources\n--------------------\n\nFor more information about testing on Android, consult the following resources.\n\n### Samples\n\n- [Android testing samples](https://github.com/android/testing-samples)\n- [Now In Android demo app](https://github.com/android/nowinandroid), which makes use of the Android testing libraries.\n\n### Codelabs\n\n- [Android Testing Codelab](/codelabs/advanced-android-kotlin-training-testing-basics)\n\nMedia\n-----"]]
