skills.rest
hitoshura25
hitoshura25COMMUNITY
Explore all skills by this author →
GitHub

android-additional-tests

Add instrumented Android tests for navigation, user flows, and onboarding.

3|1|Updated Dec 4, 2025
Search Tags:#testing#android#ui-testing#espresso#qa-automation#instrumented-tests#androidJUnit
One-click install
npx skills add https://github.com/hitoshura25/claude-devtools --skill android-additional-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-additional-tests
Source: https://github.com/hitoshura25/claude-devtools/tree/main/skills/android-additional-tests
Command: npx skills add https://github.com/hitoshura25/claude-devtools --skill android-additional-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill extends Android testing beyond the basic smoke test by providing additional instrumented tests that validate navigation, user flows, and UI interactions across the app.

Core Features & Use Cases

  • Additional instrumented tests: cover navigation paths, screen transitions, and key user flows.
  • Onboarding & flow validation: ensure onboarding steps complete without regressions.
  • Use Case: before a release, run comprehensive tests to confirm critical paths (login, main actions) are stable.

Quick Start

  • Ensure the android-e2e-testing-setup is complete and the smoke test passes.
  • Create additional test files under app/src/androidTest/kotlin/ using the provided templates and replace placeholders with your package and activity names.
  • Run tests locally: ./gradlew connectedDebugAndroidTest, or run via CI and review HTML reports in app/build/reports/androidTests/connected.

Frequently Asked Questions about android-additional-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add more Android instrumented tests beyond a basic smoke test?▼

Additional Android instrumented tests are added by creating test files under app/src/androidTest/kotlin/ using provided templates, replacing placeholders with your package and activity names to validate navigation and user flows.

What do Espresso instrumented tests cover for Android UI flows?▼

Espresso instrumented tests cover screen transitions, navigation paths, and key user flows like onboarding and login, ensuring critical app paths remain stable without regressions before a release.

Do I need an existing end-to-end testing setup to add Android UI tests?▼

Yes, an existing Android end-to-end testing setup with a passing smoke test is required. This ensures the base environment is configured correctly before extending coverage with additional instrumented tests.

How do I run connectedAndroidTest for Espresso tests in CI?▼

Run connectedAndroidTest using ./gradlew connectedDebugAndroidTest locally or integrate the command into your CI workflow. HTML test reports are generated in app/build/reports/androidTests/connected/ for review.

What are the limitations of extending Android test coverage with instrumented tests?▼

These instrumented tests require real devices or emulators to execute and focus solely on UI flows and navigation. They do not replace unit tests and require a pre-existing passing smoke test setup to function correctly.

Related Skills

Explore More Software Engineering Skills→
olehsvyrydovolehsvyrydov
13

e2e-tester

Automate end-to-end tests for web and mobile apps with Playwright and Detox.

Community
Advanced
mvillmowmvillmow
18

quality-coverage-report

Generate HTML and terminal coverage reports for Python pytest runs.

Community
Intermediate
tranceetrancee

testing-with-espresso-interop

Synchronize Jetpack Compose and Espresso UI tests within Android Activities.

Community
Advanced
IsKenKenYaIsKenKenYa
35

mobile-app-testing

Provides mobile app testing strategies and code examples for iOS and Android.

Community
Advanced