skills.rest
premex-ab
premex-abOFFICIAL
Explore all skills by this author →
GitHub

testing-setup

Analyze Android testing dependencies and define a strategy across unit, UI, screenshot, and e2e layers.

1|Updated Mar 17, 2026
Search Tags:#testing strategy#dependency injection#ui testing#android#screenshot tests#robolectric#gradle jacoco
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill testing-setup-premex-ab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-setup
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-testing-setup/skills/testing-setup
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill testing-setup-premex-ab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you analyze an existing native Android app’s testing setup and produce a practical, step-by-step plan to install testing libraries, set up infrastructure, and build unit, UI, screenshot, and end-to-end test harnesses.

Core Features & Use Cases

  • Testing audit & gap analysis: Identifies the project’s current testing stack (dependency injection, unit testing, mocking, Robolectric usage, Compose vs Views, screenshot and e2e coverage).
  • Concrete setup plan: Recommends and wires up the appropriate frameworks and configuration such as test runners, rules, DI integration, and baseline tooling like JUnit and Jacoco.
  • Test architecture guidance: Defines where tests should live (local vs instrumented), how to refactor for fakes/mocks, and how to structure unit, UI behavior, navigation, window-size/config, screenshot, and end-to-end test suites.
  • Screenshot testing references: Points to Compose Preview Screenshot Testing requirements and workflow details for creating and validating references.

Quick Start

Ask for a testing strategy plan by telling the AI: “Analyze my current Android testing setup and generate a complete strategy to cover unit, UI, screenshot, and end-to-end tests for this native app.”

Frequently Asked Questions about testing-setup

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

FAQPage Schema
How do I design an Android testing strategy for unit, UI, screenshot, and end-to-end layers?▼

To design an Android testing strategy, analyze the project's existing dependencies and architecture to produce a step-by-step plan covering unit, UI, screenshot, and end-to-end test harnesses. This includes configuring test runners, rules, and DI integration.

Where should Robolectric UI tests and instrumented tests live in an Android project?▼

Robolectric UI tests and instrumented tests require correct test source set placement to execute properly. The strategy defines where tests should live by separating local host-side Robolectric tests from instrumented tests based on their execution environment.

Does this Android testing setup work with Compose, Views, and hybrid UIs using Hilt or Koin?▼

Yes, the Android testing setup works with Compose, Views, and hybrid UIs using Hilt, Koin, Dagger, or no DI. It provides specific architecture guidance for refactoring with fakes and mocks across these different dependency injection and UI configurations.

What's the best way to configure Gradle Jacoco and screenshot testing for an Android app?▼

The best way to configure Gradle Jacoco and screenshot testing is to wire up the appropriate frameworks and baseline tooling. The setup plan includes Jacoco coverage configuration and points to Compose Preview Screenshot Testing requirements for creating and validating references.

How do I handle navigation and window-size configuration variation in Android UI tests?▼

To handle navigation and window-size configuration variation in Android UI tests, define a structured test architecture that includes controlled window-size overrides. This ensures your UI behavior, navigation, and configuration tests remain stable across different device states.

What are the limitations of using Robolectric for host-side Android UI tests?▼

Robolectric host-side Android UI tests require correct local source set placement and specific test runner configuration to avoid execution failures. The testing strategy addresses these constraints by defining clear boundaries between local Robolectric tests and instrumented device tests.

Related Skills

Explore More Software Engineering Skills→
klxiaoniuklxiaoniu
174

testing-setup

Analyze native Android projects and implement a testing strategy with a Markdown report.

Community
Advanced
ekawijayasusiloekawijayasusilo

testing-setup

Analyze Android dependencies and generate a Markdown testing strategy report.

Community
Advanced
fornewidfornewid
5

https://developer.android.com/agents/skills/testing/testing-setup/skill

Audit Android project dependencies and configure testing frameworks.

Community
Advanced
yash-gargyash-garg

testing-setup

Analyze Android projects and create testing strategies for unit, UI, screenshot, and end-to-end tests.

Community
Advanced