What is testing-setup?

A process for examining and setting up tests in native Android apps, including code tests, user-interface tests, screenshot comparisons, and full app flows.

It helps inspect dependencies and app UI technology, then set up libraries, test harnesses, local or device-based UI tests, screenshot tests, and end-to-end tests.

It identifies the app’s existing test tools and fills in missing infrastructure so different kinds of behavior can be checked reliably.

How arindamxd/camerax-android configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to arindamxd/camerax-android. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/arindamxd/camerax-android/master/.agents/skills/testing-setup/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/arindamxd/camerax-android

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/arindamxd/camerax-android/testing-setup/github.svg)](https://agentmods.dev/skills/arindamxd/camerax-android/testing-setup)

Your own site

<a href="https://agentmods.dev/skills/arindamxd/camerax-android/testing-setup"><img src="https://agentmods.dev/badge/skills/arindamxd/camerax-android/testing-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arindamxd/camerax-android/testing-setup"><img src="https://agentmods.dev/badge/skills/arindamxd/camerax-android/testing-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,037 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.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.02037
Opus 5.5	$0.00017	$0.00815
Sonnet 5.5	$0.00009	$0.00407
Haiku 4.5	$0.00004	$0.00204

Measured 2mo ago against content hash acc74408bd47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-setup 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 2mo 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.

Origin

This is a copy

100% identical to testing-setup — 137 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/testing-setup/SKILL.md · 159 lines

How it starts

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

Step 1: analyze the current testing setup

To understand the testing setup of an existing project, look for these dependencies in the libs.versions.toml file, or build files:

Dependency Injection framework used. Examples: Hilt, Koin, Anvil, vanilla Dagger...
Unit (local) testing framework this project uses, Example JUnit4, JUnit5...
Mocking framework (if any) used for unit tests, and for Instrumented and UI tests. Examples: Mockito, Mockk...
Robolectric. It can be used in 3 ways:
1. Used in unit tests to have fakes for platform entities
2. To run behavior UI tests without a device or emulator. For example, used to run Espresso or Compose tests.
3. To do screenshot testing with Roborazzi
Is the app 100% Compose, Views or hybrid?
Behavior UI tests:
1. Compose Tests (androidx.compose.ui:ui-test-*)
2. Espresso Tests for Views. Might use wrappers like Kaspresso. Dependencies: androidx.test.espresso:espresso-core, androidx.test:runner, androidx.test:rules.
Screenshot tests can be:
1. Instrumented (device-based). For example, using Dropshots.
2. Based on Robolectric, so they run locally. For example, using Roborazzi.
3. Based on LayoutLib, so they run locally. For example, Paparazzi, or the Compose Preview Screenshot Testing tool.
End to end tests (also known as Release Candidate tests) always run on device and use high-level frameworks such as UIAutomator, Appium, or Robotium.
Generate a Markdown report with the analysis

Step 2: Set up Dependency Injection frameworks for testing

If there is no Dependency Injection framework, install one: if it's a multiplatform application, ask the user whether they want to install Koin, or kotlin-inject. If it's not multiplatform, install Hilt.

Install the testing dependencies (for example com.google.dagger:hilt-compiler that should be applied with a kspAndroidTest configuration).

[!IMPORTANT] Important: Always consult the documentation of the applicable framework to learn about testing (for example: Hilt testing guide, Koin Instrumented tests).

Read the full file on GitHub · 159 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 159 lines · 43 tokens per session scan A acc74408bd47

Subscribe to this mod's changes

testing-setup is a skill published in the GitHub repository arindamxd/camerax-android (132 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,037 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to testing-setup, differing in 137 lines, and is treated as a copy.

E2E testing Testing Unit testing android camerax jetpack kotlin

testing-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
testing-setuparindamxd/camerax-android	Skill	132	1mo ago	Apache-2.0	A	43	Claude Code, Codex
test-triageniki914/zafiro	Skill	340	4d ago	MIT	A	71	Claude Code, Codex
test-hang-watchdogniki914/zafiro	Skill	340	4d ago	MIT	A	66	Claude Code, Codex
zafiro-qaniki914/zafiro	Skill	340	4d ago	MIT	A	71	Claude Code, Codex
testing-expertJosephSanjaya/skills	Skill	5	8d ago	MIT	A	115	Claude Code, Codex
ios-testingTalissonVitorino/kmp-ios-skills	Skill	16	2mo ago	MIT	A	69	Claude Code, Codex
mobile-testingTalissonVitorino/kmp-ios-skills	Skill	16	2mo ago	MIT	A	102	Claude Code, Codex

camerax-android: Skill for Claude Code