qa-testing-android
SolidAndroid testing with Espresso, UIAutomator, and Compose Testing. Use when building layered test strategy, device matrix, or CI integration.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- vasilyu1983
- Repository
- vasilyu1983/AI-Agents-public
- Created
- 10 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
android-testing
JUnit + Robolectric unit tests, Compose UI tests, screenshot tests, and Espresso for legacy views.
espresso
When the user wants to design, implement, debug, or stabilize Espresso tests for native Android UI automation. Use when the user mentions "Espresso," "onView," "ViewMatchers," "withId," "IdlingResource," "ActivityScenario," "ActivityScenarioRule," "AndroidJUnitRunner," "androidx.test," "instrumented tests," "Espresso Intents," "Espresso Web," or "@RunWith(AndroidJUnit4)." For cross-platform mobile see appium. For iOS-native see xcuitest. For React Native see detox. For YAML-driven flows see maestro.
android-testing
Android test strategy per Google's testing docs: test scopes, fakes over mocks, ViewModel and Flow tests, Hilt test bindings, Room DAO tests, Robolectric, Roborazzi and Compose Preview screenshot tests. Use when planning or writing unit, integration, Hilt, Room, or screenshot tests, or when a StateFlow test sees only its initial value or a local test throws Method not mocked.