android-test-suite-apply

Audits, plans, and applies Android test suite and CI wiring per the test-automation spec.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/nolte/claude-android-engineering --skill android-test-suite-apply-nolte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-test-suite-apply
Source: https://github.com/nolte/claude-android-engineering/tree/main/skills/android-test-suite-apply
Command: npx skills add https://github.com/nolte/claude-android-engineering --skill android-test-suite-apply-nolte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Existing Android projects often accumulate test suites with sleeps, mocks of own code, hard-coded dispatchers, and ad-hoc CI workflows that drift from local runs. This Skill brings an existing app's test suite and CI wiring in line with a governing test-automation spec through a controlled audit-plan-apply workflow where every write is approved per item. ## Core Features & Use Cases - Read-only audit: Scans all test sources, build scripts, and workflows, then reports severity-classified findings (Critical/Warning/Suggestion/Info) with file, line, and spec section. - Strategy recording: Walks the operator through pyramid, runner, doubles, screenshot, and CI decisions and writes them to project/test-strategy.md. - Infrastructure apply: Adds MainDispatcherRule, fakes, Robolectric Compose hosting, the forced-size matrix, the Roborazzi screenshot lane with accessibility checks, and one CI workflow running single-variant unit tests plus lint via Taskfile targets. - Use Case: Ask it to harden a suite full of Thread.sleep calls and mockk-based repository mocks; it audits, records a strategy, replaces sleeps with virtual time and mocks with fakes, wires CI, and closes on a green ./gradlew build and task check. ## Quick Start Ask the assistant to audit my Android app's test suite against the test-automation spec and then wire the unit tests and lint into a single GitHub Actions workflow.

Frequently Asked Questions about android-test-suite-apply

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

FAQPage Schema
How do I audit my Android test suite against a spec?

Run the audit operation, which scans all src/test and src/androidTest sources, build scripts, and CI workflows read-only. It reports severity-classified findings with file, line, and the violated spec section, writing nothing to the project.

How to add Roborazzi screenshot tests to an Android project?

The apply operation wires the Roborazzi plugin, per-module golden directories, and verify tasks into the build. Goldens are recorded on CI/Linux only, never on the workstation, because workstation renders drift on font antialiasing.

Should I use fakes or mocks for Android unit tests?

The governing spec mandates fakes over mocks: mocking project-owned repositories or use cases is a Critical finding, while mocking is permitted only at true system boundaries like platform APIs. The skill replaces mocks of own code with hand-written fakes after per-file confirmation.

Why does my ViewModel test fail with Main dispatcher not initialized?

runTest does not provide Dispatchers.Main, so a ViewModel launching on viewModelScope fails without a MainDispatcherRule. The fix is applying the TestWatcher-based rule, not scattering Dispatchers.setMain across test methods.

When should I not use this test suite skill?

Do not use it to scaffold a new project, write a feature's own tests, or diagnose a red test; those route to android-project-scaffold, android-feature-implement, and android-debugging respectively. It owns test infrastructure, strategy, and CI wiring only.