agentmods.dev

choosing-test-rule-vs-runtest

choosing-test-rule-vs-runtest is a skill for Claude Code, Codex from skydoves/android-testing-skills. It costs 205 tokens per session (4,387 once invoked), scanned A, original, Apache-2.0.

A guide to choosing one correct entry point for a Jetpack Compose UI test, such as a JUnit rule or a suspending test block.

In plain words
What is it for?
Use it when starting or migrating a Compose test, choosing the right rule for an Activity, or diagnosing setup and timing errors.
Why use it?
It prevents two test environments from being created at once and explains differences between older and newer Compose testing APIs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 319repo +1 3mo ago A scan SkillSpector: pass 205 tokens original Apache-2.0

Good fit Use it when starting or migrating a Compose test, choosing the right rule for an Activity, or diagnosing setup and timing errors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest
View source ↗ skydoves/android-testing-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add skydoves/android-testing-skills --skill choosing-test-rule-vs-runtest
Clone the repo
git clone --depth 1 https://github.com/skydoves/android-testing-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for choosing-test-rule-vs-runtest

README.md
[![agentmods](https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest/github.svg)](https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest)
Your own site
<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for choosing-test-rule-vs-runtest

Your own site · 80×15
<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-test-rule-vs-runtest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 205 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00205 $0.04387
Opus 5 $0.00102 $0.02194
Sonnet 5 $0.00041 $0.00877
Haiku 4.5 $0.00020 $0.00439

Measured 11d ago against content hash 432ec6cd9aca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

choosing-test-rule-vs-runtest scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

compose/setup/choosing-test-rule-vs-runtest/SKILL.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Choosing Test Rule vs runComposeUiTest — One Entry Point Per Test

Compose ships two parallel test entry points: a JUnit4 TestRule (createComposeRule() and friends) and a multiplatform suspending lambda (runComposeUiTest { }). Each one independently sets up the recomposer, MainTestClock, and IdlingResource. Mixing them in a single test produces double-environment bugs that are hard to diagnose. This skill picks the right one and surfaces the v1 → v2 deprecation that bites every existing codebase.

When to use this skill

  • The user is starting a new Compose UI test and is choosing between createComposeRule() and runComposeUiTest { }.
  • The IDE shows a deprecation WARNING on import androidx.compose.ui.test.junit4.createComposeRule or import androidx.compose.ui.test.runComposeUiTest.
  • The user reports tests passing on v1 entry points but breaking after migrating because LaunchedEffects no longer run synchronously.
  • The user has a custom ComponentActivity subclass and is unsure between createAndroidComposeRule and createEmptyComposeRule.
  • The user reports IllegalStateException: setContent can only be called once per ComposeTestRule or "the launched Activity already calls setContent".
  • The user is writing Compose Multiplatform (KMP) tests and needs the suspending entry point.

When NOT to use this skill

  • The dependencies do not yet compile — start with ./configuring-test-dependencies/SKILL.md.
  • The choice is host vs device, not rule vs lambda — see ./setting-up-host-vs-device-tests/SKILL.md.
  • The test compiles and runs but flakes on idle/animation — see ../../synchronization/synchronizing-with-idle/SKILL.md and ../../synchronization/testing-animations-deterministically/SKILL.md.

Prerequisites

  • androidx.compose.ui:ui-test, androidx.compose.ui:ui-test-junit4, and (for createComposeRule() / runComposeUiTest { }) androidx.compose.ui:ui-test-manifest on the right configurations — see ./configuring-test-dependencies/SKILL.md.
  • A test class with JUnit4 on the classpath if the developer chooses the rule path.
  • Working knowledge that MainTestClock and the recomposer share one kotlinx.coroutines.test.TestCoroutineScheduler.

Read the full file on GitHub · 274 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 274 lines · 205 tokens per session scan A 432ec6cd9aca

Subscribe to this mod's changes

choosing-test-rule-vs-runtest is a skill published in the GitHub repository skydoves/android-testing-skills (319 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 205 tokens to every session and 4,387 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

E2E testingMobileTesting
Related

Other skills, from other repositories

android-ui-journey-testing

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

sickn33/agentic-awesome-skills · 27 tokens

android_ui_verification

Automated end-to-end UI testing and verification on an Android Emulator using ADB.

sickn33/agentic-awesome-skills · 22 tokens

solopi-ai

A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.

alipay/SoloPi · 127 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

eas-simulator

EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…

expo/skills · 249 tokens

test-native-extension

Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…

microsoft/power-platform-skills · 211 tokens