android-additional-tests_skill

Overview

This skill adds optional, comprehensive Android instrumented tests beyond the basic smoke test. It provides examples for package-level sanity checks, screen-specific Espresso tests, end-to-end user flows, and an optional GitHub Actions workflow to run tests on CI. Use it when you need stronger UI and navigation validation for larger or more complex apps.

How this skill works

The skill scaffolds Kotlin Android instrumented tests under app/src/androidTest, including an ExampleInstrumentedTest for package and context checks, screen tests using ActivityScenarioRule and Espresso, and flow tests that model end-to-end user journeys. It also provides an optional GitHub Actions workflow that boots an emulator and runs ./gradlew connectedDebugAndroidTest, and instructions to view the HTML test report.

When to use it

• You need comprehensive coverage for specific user flows or onboarding.
• You must validate complex navigation patterns and UI interactions.
• You want screen-level assertions (views present, accessibility checks).
• You plan to run instrumented tests in CI and capture HTML reports.
• Skip if you only require the basic smoke test or a minimal setup.

Best practices

• Verify package and main activity names before running tests to avoid package mismatch errors.
• Replace TODO placeholders with real view IDs and navigation logic to prevent false failures.
• Disable animations on emulators or devices to stabilize UI tests.
• Keep tests focused and deterministic: mock network where possible and seed consistent test data.
• Run tests locally on an emulator before adding them to CI to iterate quickly.

Example use cases

• Assert the app package and context are correct as an extended sanity check.
• Verify main activity launches and critical views (toolbar, main content) display.
• Automate onboarding flows to ensure new users reach the main screen.
• Test navigation buttons and destination screens using Espresso click and assert patterns.