Audit Coverage Gaps
Testing & Qualityaudit-coverage-gapsAudit Coverage Gaps is an Agent Skill for testing & quality published in the ben-manes/caffeine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Discover test coverage gaps that could hide correctness defects
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/ben-manes/caffeine/blob/HEAD/.claude/skills/audit-coverage-gaps/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/audit-coverage-gaps, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Assume the existing tests miss at least one real defect.
-
For each public method, identify the hardest-to-test edge cases:
- Null values (where permitted)
- Maximum/minimum weight
- Zero-duration expiration
- Mapping functions that return the same instance
- Mapping functions that throw
- Weighers that throw
- Expiry callbacks that throw
- CompletableFuture values (async cache edge cases)
- Keys/values with adversarial hashCode/equals
-
For each edge case, trace the code path. Does the code handle it correctly?
-
Identify combinatorially hard behavioral dimensions:
- Operation A on expired entry during concurrent operation B
- Exception in user callback X while holding lock Y
- GC collecting reference R between code points P and Q
- Fast path falls through to slow path under contention (e.g., entry appears expired on fast path, recovers under lock on slow path)
- Async cache: future completes between check and action (e.g., isComputingAsync returns true, but future completes before the code that depends on that check executes)
-
For each candidate gap, provide a minimal test case with the specific cache configuration and thread interleaving needed to reach the code path.
Priority ordering:
- Paths involving the catch-commit-rethrow pattern (doComputeIfAbsent, remap)
- Slow paths reachable only via contention (synchronized blocks after optimistic checks)
- Interactions between expiration and the async value lifecycle (ASYNC_EXPIRY, isComputingAsync)
Focus only on behavioral coverage gaps that could hide correctness bugs.