configuring-test-dependencies

Configure Gradle dependencies for Jetpack Compose UI and instrumentation tests.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill configuring-test-dependencies-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configuring-test-dependencies
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/compose/setup/configuring-test-dependencies
Command: npx skills add https://github.com/trancee/MeshLink-template --skill configuring-test-dependencies-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common build-time and runtime failures in Jetpack Compose testing, such as ActivityNotFoundException, unresolved createComposeRule symbols, and incorrect manifest merging.

Core Features & Use Cases

  • Dependency Matrix Management: Provides the exact configuration for instrumentation (androidTest) and host (test) source sets.
  • Manifest Troubleshooting: Fixes missing ComponentActivity declarations by correctly applying the ui-test-manifest artifact.
  • Use Case: Use this skill when your Compose UI tests fail to launch or compile, or when you need to integrate Robolectric for fast JVM-based testing.

Quick Start

Use the configuring-test-dependencies skill to audit my build.gradle.kts file and suggest the correct dependency configuration for my Compose UI tests.

Frequently Asked Questions about configuring-test-dependencies

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

FAQPage Schema
Why does my Jetpack Compose UI test throw ActivityNotFoundException?

Jetpack Compose UI tests throw ActivityNotFoundException when the test manifest lacks ComponentActivity declarations. Applying the correct ui-test-manifest artifact resolves this missing component declaration during instrumentation testing.

How do I fix unresolved createComposeRule symbols in Android test source sets?

Unresolved createComposeRule symbols occur when the Compose UI testing Gradle dependencies are missing. Configuring the correct dependency matrix for the androidTest source set resolves these compilation failures for Jetpack Compose instrumentation tests.

What Gradle dependencies are needed to run Robolectric host-based tests for Compose?

Running Robolectric host-based tests for Compose requires configuring the correct dependency matrix for the test source set. This separates JVM-based host testing from instrumentation testing to resolve missing test rule symbols.

Can I use the same Gradle dependency configuration for instrumentation and host tests?

Instrumentation and host tests require correct source set separation in your Gradle configuration. Distinct dependency matrices must be applied for androidTest and test source sets to support both instrumentation and Robolectric JVM-based testing.

How do I audit my build.gradle.kts file for the correct Compose UI test dependencies?

Auditing a build.gradle.kts file for Compose UI test dependencies involves checking the instrumentation and host source set configurations. This ensures the correct dependency matrix is applied to resolve build-time and runtime test failures.