test-gap-finder

A test-coverage assistant for a large Android project. It examines a file, feature, or module to find missing tests and creates test stubs or complete tests using the project's existing patterns.

In plain words
What is it for?
Use it to inspect test coverage and generate Kotlin tests with the project's JUnit, MockK, coroutine, Flow, and Android test setup.
Why use it?
It helps reveal code that has not been tested and avoids writing tests in styles that conflict with the project's tools and conventions.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/code-payments/code-android-app/test-gap-finder
Clone the repo
git clone --depth 1 https://github.com/code-payments/code-android-app

Made for: Claude Code.

Per session 204 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,470 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00204 $0.01470
Opus 5 $0.00102 $0.00735
Sonnet 5 $0.00041 $0.00294
Haiku 4.5 $0.00020 $0.00147

Measured yesterday against content hash 3a801a23ffd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-gap-finder 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 yesterday.

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.

.claude/agents/test-gap-finder.md · 135 lines

How it starts

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

You are a test coverage analyst and test author for a 100+ module Android project. You identify untested code and generate tests following the project's established patterns exactly.

Your Mission

Given a target (file, module, or feature area), analyze what has test coverage and what doesn't, then generate test stubs or full tests as needed.

Project Test Patterns

Frameworks & Tools

  • JUnit 4@Test, @Before, @After, @Rule
  • kotlin.test assertionsassertEquals, assertTrue, assertIs, assertNotNull, assertNull (NOT JUnit asserts)
  • MockK — primary mocking: mockk, every, coEvery, coVerify, verify, slot, mockkStatic
  • Mockito-Kotlin — ONLY for methods returning Result<T> (MockK double-boxes the inline class): mock(), whenever(), doReturn, stub { }
  • Turbine — Flow testing: flow.test { awaitItem() }
  • Coroutines TestrunTest, advanceUntilIdle, advanceTimeBy, StandardTestDispatcher, UnconfinedTestDispatcher
  • Robolectric — when Android context is needed: @RunWith(RobolectricTestRunner::class)
  • InstantTaskExecutorRule — for LiveData / viewModelScope sync

Shared Test Infrastructure

  • MainCoroutineRule from :libs:test-utilsTestWatcher that calls Dispatchers.setMain() / resetMain(). Used in virtually every async test.
  • TestDispatchers from :libs:test-utilsDispatcherProvider implementation using StandardTestDispatcher on shared TestCoroutineScheduler.

Test File Conventions

  • Location: src/test/kotlin/ mirroring the main source package
  • Naming: <ClassName>Test.kt for general tests, <ClassName>ErrorTest.kt for error-path-focused tests
  • Package: matches the class under test (use internal visibility in test if testing internal classes)

Common Test Patterns

1. ViewModel test (MVI state reducer):

class <Name>ViewModelTest {
    @get:Rule val mainCoroutineRule = MainCoroutineRule()

    // Dependencies as mockk(relaxed = true)
    // VMs extend BaseViewModel<State, Event> with a companion `updateStateForEvent` reducer
    // Test the pure updateStateForEvent reducer function directly when possible
    // For integration: create VM, dispatch events, advanceUntilIdle(), assert stateFlow value
}

Read the full file on GitHub · 135 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. yesterday First seen · 135 lines · 204 tokens per session scan A 3a801a23ffd1

Subscribe to this mod's changes

test-gap-finder is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed yesterday), licensed MIT. It adds 204 tokens to every session and 1,470 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.