android-testing

Standardize Android JVM, instrumented, and UI tests with JUnit, MockK, and Turbine.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill android-testing-dimitriremoiville
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-testing
Source: https://github.com/dimitriRemoiville/cc-mobile/tree/main/plugins/cc-mobile-android/skills/android-testing
Command: npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill android-testing-dimitriremoiville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android projects struggle with inconsistent testing practices and maintenance of test suites. This Skill provides a curated set of testing patterns, templates, and guidelines to standardize unit, UI, and integration tests across the codebase.

Core Features & Use Cases

  • JUnit-based unit tests with MockK and coroutines test rules
  • Flow and Compose UI testing with Turbine and Compose test rules
  • Hilt instrumentation tests for integration points and test doubles
  • Guidance on organizing tests, test data, and lifecycle management

Quick Start

Run the Gradle task to execute JVM unit tests, instrumented tests, and UI tests following the patterns described above.

Frequently Asked Questions about android-testing

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

FAQPage Schema
How do I set up Android testing for ViewModels and repositories using coroutines?

Android testing for ViewModels and repositories uses JUnit, MockK, and coroutines test rules to ensure deterministic execution. This Skill provides standardized patterns and templates to structure these JVM unit tests reliably across your codebase.

What's the best way to test Compose UI and Flows in Android apps?

Testing Compose UI and Flows in Android apps is best handled with Turbine and Compose test rules. This approach provides standardized templates for asserting UI component states and Flow emissions consistently.

Do I need MockK and Turbine to standardize my Android test suite?

Yes, you need MockK for mocking and Turbine for Flow testing to standardize your Android test suite. These dependencies are required alongside JUnit and Hilt testing artifacts to execute the deterministic patterns provided by this Skill.

Why are my Android instrumented tests failing due to inconsistent testing practices?

Android instrumented tests often fail due to inconsistent lifecycle management and test data organization. This Skill solves the challenge by providing curated guidelines and standardized patterns for maintaining reliable test execution across your project.

Can I use this Skill for JVM unit tests in my Android project?

Yes, you can use this Skill for JVM unit tests in your Android project. It provides JUnit-based templates with MockK and coroutines test rules to standardize unit, UI, and integration tests across the codebase.