skills/ HoangNguyen0403/agent-skills-standard

android-testing

Write Android unit, Compose UI, and Hilt-integrated tests. Use when designing test behavior with MockK or coroutine test utilities; defer database/WorkManager-specific recipes to the owning feature skill.

0
Installs
—
Rating
—
Success rate
3
Files scanned
Scan passedmobile
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

3 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 ade38f51c0c42271… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Android Testing Standards

Priority: P0 (CRITICAL)

The Four-Pillar Test Value Framework

Qualitative reasoning framework to evaluate unit test value:

  • Protection against Regressions: Catches real defects; a test passing during failure offers zero protection.
  • Resistance to Refactoring: Decoupled from internal implementation; zero false alarms on internal refactorings.
  • Fast Feedback: Executes in milliseconds; rapid local TDD feedback loop.
  • Maintainability: Clean AAA structure, high readability, zero boilerplate duplication. Avoid inventing arbitrary numeric scores (e.g. P * R * F * M) statically without empirical measurement.

Core Rule Anchors

  • [MOB-TEST-01] Tripartite Naming: Name tests Method_Scenario_ExpectedBehavior (e.g. submitOrder_whenCreditLimitExceeded_displaysBlockedBanner).
  • [MOB-TEST-02] State & ViewModel Invariant Rule: Assert UI state transitions (e.g. StateFlow/UiState via Turbine test {}); ban asserting 30-property boilerplate state copies.
  • [MOB-TEST-03] Entity Invariant & Serialization Rule: Test calculations, validations, domain invariants, and non-trivial serialization/parsing or error mapping. Ban testing auto-generated code, trivial getters, or echo tests repeating literal assignments.
  • [MOB-TEST-04] Contract Testing Rule: Repositories and data sources must be tested for contract compliance and error mapping. Ban 1:1 pass-through mock echoing (coEvery { dataSource.get() } returns x; repo.get() == x).
  • [MOB-TEST-05] Bug-First Regression Lock: Every PR fixing a bug ticket or with title fix(...) must introduce a failing test reproducing the defect before fixing it.

Implementation Guidelines

Unit Tests

  • Scope & Async: ViewModels, Usecases, Repositories, Utils. Use runTest with MainDispatcherRule. Mock with MockK or fakes.
  • Coverage: Coverage is diagnostic and project-configured; verify risk-weighted critical paths rather than padding code for an arbitrary percentage.

UI Integration Tests (Instrumentation)

  • Scope & DI: Composable Screens, Navigation flows. Use createAndroidComposeRule + Hilt (HiltAndroidRule). Fake repositories via @TestInstallIn.
  • Negative Assertions: Add negative assertions only when absence is part of the business contract.

Anti-Patterns & Banned Smells

  • [MOB-TEST-01] Vague names: Banish non-descriptive test names.
  • [MOB-TEST-02] Brittle state copies: Ban asserting 30-property boilerplate state copies; use focused state assertions or Turbine.
  • [MOB-TEST-03] Echo tests: Ban testing auto-generated code, trivial getters, or repeating literal assignments.
  • [MOB-TEST-04] Pass-through mock echoing: Ban 1:1 pass-through mock echoing and shallow assertions without contract checks.
  • [MOB-TEST-05] Missing bug reproduction: Ban bug fix PRs without reproduction tests.
  • No Real Network / Thread.sleep: Fake repositories in DI; use IdlingResource or composeTestRule.waitUntil for async timing.

References

Files

3
7.7 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related mobile skillsscan passed