skills.rest
peterbamuhigire
peterbamuhigireCOMMUNITY
Explore all skills by this author →
Website𝕏@peterbamuGitHub

android-tdd

Orchestrate Android TDD workflows with Red-Green-Refactor cycles and CI integration patterns.

23|7|Updated Jan 23, 2026
Search Tags:#workflow#testing#tdd#architecture#red-green-refactor#android#ci
One-click install
npx skills add https://github.com/peterbamuhigire/skills-web-dev --skill android-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-tdd
Source: https://github.com/peterbamuhigire/skills-web-dev/tree/main/android-tdd
Command: npx skills add https://github.com/peterbamuhigire/skills-web-dev --skill android-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Android teams often struggle to maintain quality and consistency when adopting Test-Driven Development for Android features; this Skill provides a structured workflow, a clear test-pyramid guideline, and CI integration patterns to standardize practice across projects.

Core Features & Use Cases

  • Red-Green-Refactor cycle guidance to ensure incremental, test-first development.
  • Test Pyramid (70/20/10) guidance across Unit / Integration / UI tests.
  • Layer-specific testing strategies for Domain/Model, ViewModel, Repository, and UI layers, plus CI recommendations.
  • CI integration patterns and example pipelines to enforce test gates and coverage.

Quick Start

Write a failing unit test for a small Android feature, implement the minimal code to pass it, then refactor while all tests remain green.

Frequently Asked Questions about android-tdd

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

FAQPage Schema
How do I enforce a consistent Red-Green-Refactor cycle for Android feature development?▼

Android TDD workflows enforce a consistent Red-Green-Refactor cycle by guiding you to write a failing test, implement minimal code to pass it, and then refactor while all tests remain green. This ensures incremental, test-first feature development.

What is the recommended test pyramid ratio for Android unit, integration, and UI tests?▼

The recommended test pyramid ratio for Android tests is 70/20/10 across Unit, Integration, and UI tests. Adhering to this distribution ensures fast execution and broad coverage across Domain, ViewModel, Repository, and UI layers.

How do I integrate TDD test gates and coverage enforcement into Android CI pipelines?▼

You can integrate Android TDD into CI pipelines using specific integration patterns and example pipelines that enforce test gates and coverage checks. This standardizes test quality and prevents merging untested feature code.

Does Android TDD provide layer-specific testing strategies for ViewModels and Repositories?▼

Android TDD provides layer-specific testing strategies for Domain, ViewModel, Repository, and UI layers. These strategies ensure tests target the correct architectural boundaries, improving overall test quality and maintainability.

When should I apply Test-Driven Development workflows in my Android project?▼

You should apply Android TDD workflows during feature development, code reviews, onboarding, and CI pipeline configuration. Applying TDD in these scenarios standardizes practice and improves test consistency across the project.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

android-architecture

Enforce MVVM, clean architecture, and Hilt dependency injection in Android projects.

Official
Advanced
ResearchMonkeyResearchMonkey

review-tests

Analyze test quality and coverage to identify gaps and flaky tests.

Community
Intermediate
lpjhelderlpjhelder

tdd

Enforce failing tests before production code across RED, GREEN, and REFACTOR phases.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

ATDD 助手

Guide teams through ATDD workflows with Given-When-Then acceptance criteria.

Community
Intermediate