android-ui-testing

Test Android/KMP Compose UI with real ViewModels and E2E flows.

6|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/PL-Coding-GmbH/Skills --skill android-ui-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-ui-testing
Source: https://github.com/PL-Coding-GmbH/Skills/tree/main/skills/android-ui-testing
Command: npx skills add https://github.com/PL-Coding-GmbH/Skills --skill android-ui-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires androidx.compose.ui:ui-test-junit4, createAndroidComposeRule, AssertK, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of writing effective UI tests for Android/KMP using Compose and real ViewModel integration, ensuring comprehensive coverage and reliable test outcomes.

Core Features & Use Cases

  • Compose UI Testing: Supports testing of Compose UI on real devices or emulators with createAndroidComposeRule.
  • Real ViewModel Integration: Enables integration tests with real ViewModels and I/O collaborators.
  • Feature E2E Testing: Facilitates end-to-end testing of complete user flows.
  • Robot Pattern for E2E: Offers a pattern for structuring complex E2E tests.
  • Compose 1.11.0 Dispatcher Changes: Guides on handling the dispatcher change for Compose 1.11.0+.
  • Use Case: Ideal for testing a complex navigation flow with multiple states and user interactions.

Quick Start

Use the android-ui-testing skill to perform a full E2E test on the login feature of your app.

Frequently Asked Questions about android-ui-testing

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

FAQPage Schema
How do I write UI tests for Android Compose with real ViewModel integration?

To write UI tests for Android Compose with real ViewModel integration, you use instrumentation libraries like `createAndroidComposeRule` to test UI components alongside actual ViewModels and their I/O collaborators for reliable E2E coverage.

What is the robot pattern for Android E2E testing?

The robot pattern for Android E2E testing is a structural approach for organizing complex test suites. It separates test interactions from assertions, making it easier to maintain and read end-to-end tests for complete user flows in Compose.

Does Android UI testing work with Kotlin Multiplatform (KMP) applications?

Yes, Android UI testing supports Kotlin Multiplatform (KMP) applications. It facilitates comprehensive Compose UI testing on real devices or emulators, ensuring reliable test outcomes across shared KMP codebases using specific Compose UI test libraries.

Do I need Android instrumentation to test Compose UI?

Yes, you need Android instrumentation to test Compose UI. The testing process requires specific Compose UI test libraries like `androidx.compose.ui:ui-test-junit4` to run reliably on real devices or emulators.

How do I handle Compose 1.11.0 dispatcher changes in UI testing?

To handle Compose 1.11.0 dispatcher changes in UI testing, this Skill provides specific guidance on adapting your test configurations. It ensures your Compose UI tests remain compatible with the updated dispatcher behavior introduced in version 1.11.0+.

What's the best way to structure complex navigation flow tests in Compose?

The best way to structure complex navigation flow tests in Compose is using the robot pattern for E2E suites. This approach organizes multiple states and user interactions into maintainable, comprehensive end-to-end tests with real ViewModel integration.