agentsclimarketplace
Sign in

Testing

Skill GDvega/super-android-kotlin-firebase-skill/skills/testing

Use for Android unit tests, fake repositories, coroutine tests, Flow tests, Compose UI tests, instrumented tests, ADB-driven tests and Firebase Emulator tests.From its SKILL.md

Install
npx -y skills add GDvega/super-android-kotlin-firebase-skill --skill testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 615 tokens by cl100k_base, as published. Nobody here has run it

Purpose

Create high-value tests with low fragility across Android layers.

When to use

  • Adding or reviewing tests.
  • Testing ViewModels, Flow or coroutines.
  • Testing Compose UI or accessibility.
  • Testing Firebase rules/functions with Emulator Suite.

Inputs to inspect

  • Behavior under test.
  • Existing test dependencies and source sets.
  • Repository fakes or data builders.
  • Gradle tasks and CI constraints.

Required workflow

  1. Choose the lowest useful test level first.
  2. Create fakes for behavior-focused tests.
  3. Use coroutine test APIs and virtual time.
  4. Add Compose UI/instrumented tests only for critical flows.
  5. Run the relevant Gradle task and report results.

Rules

  • No Thread.sleep.
  • Prefer fakes over mocks when state transitions matter.
  • Test loading, success, empty, error and permission-denied states.
  • Use Firebase Emulator for rules when available.
  • Keep UI tests focused.

Related existing skills

Local skills to invoke

  • debugging
  • gradle-build
  • firebase-emulator-ci
  • jetpack-compose
  • code-review-refactor

External companion skills to use when installed

Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.

  • skydoves/android-testing-skills — use for deeper Android or Compose UI testing, semantics, assertions or test workflow guidance.
  • android/skills — use for official Android workflow alignment around edge-to-edge, adaptive UI, Navigation 3, R8, AGP or testing setup.

Files commonly touched

  • src/test
  • src/androidTest
  • ViewModel tests
  • repository tests
  • Compose tests
  • rules tests

Commands to validate

./gradlew test
./gradlew connectedDebugAndroidTest
./gradlew lint
firebase emulators:exec "npm test"
adb logcat

Common mistakes to avoid

  • Only testing happy path.
  • Using UI tests for pure logic.
  • Over-mocking repositories.
  • Ignoring source set setup.

Checklist

  • Test level chosen.
  • Fakes/data builders exist.
  • Coroutine/Flow deterministic.
  • Firebase rules tested when relevant.
  • Command executed or explained.

Example prompts

  • Use $super-android-kotlin-firebase to generate ViewModel and Compose UI tests.
  • Use $super-android-kotlin-firebase to audit missing tests in this feature.

Expected response style

Respond with: brief diagnosis, change plan, affected files, code or diff summary, validation commands, tests added or recommended, risks, and next step. For review tasks, lead with findings ordered by severity.

References

  • ../../docs/audits/FUENTES_LOCALES.md
  • references/android-testing-strategy.md
  • templates/unit-test-template.md
  • templates/compose-ui-test-template.md

What ships with it: 3 files

1.1 KB alongside SKILL.md

references/

templates/

Gives 0 of the 12 instructions most test skills give in 615 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

  • Close the browser when donein 55 of 964, across 12 files
  • Wait for network idle statein 51 of 964, across 6 files
  • Launch Chromium in headless modein 49 of 964, across 6 files
  • Use descriptive selectors for elementsin 49 of 964, across 6 files
  • Run provided scripts with help flag firstin 49 of 964, across 6 files
  • Add appropriate explicit waitsin 48 of 964, across 5 files
  • Use bundled scripts as black boxesin 46 of 964, across 3 files
  • Do not read script source codein 46 of 964, across 3 files
  • Use sync playwright for scriptsin 46 of 964, across 3 files
  • Inspect dom before executing actionsin 46 of 964, across 3 files
  • Run the full test suitein 37 of 964
  • Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

  • Create fakes for behavior-focused tests
  • Use coroutine test APIs and virtual time
  • Add Compose UI tests only for critical flows
  • Run the relevant Gradle task and report results
  • Test loading, success, empty, error, and permission-denied states
  • Keep UI tests focused

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.