domains / families / software-engineering / find-untested-sources

find-untested-sources

separate

MANDATORY for static source-to-test pairing: find or list source files/modules without corresponding tests, or suggest test locations from repository structure. Invoke even for a tiny package; do not substitute manual globbing. Uses Roslyn for C#/.NET and tree-sitter for Python, TS/JS, Go, Java, Rust, Ruby, Kotlin, Swift, PowerShell, and C++. DO NOT USE FOR: real line/branch/Cobertura data, coverage-backed test priorities, CRAP risk, or grading existing tests.

When to use

• Coverage tools answer "which lines were executed?" — they require a green build and a passing test run, which is minutes-to-tens-of-minutes on a real repo. The question this skill answers is different and much cheaper: > _Which source file…
• User asks "where should I add tests based on source pairing?", "which files
• Before invoking a test-generation agent, to produce a source-pairing worklist.
• After generating tests, to verify each new test file pairs to a source file.
• To enumerate "weakly paired" source files (only one referring test) for

When not to use

• **Line/branch coverage** — use `coverage-analysis`.
• **Priorities derived from real coverage data** — use `coverage-analysis`.
• **CRAP-score / risk hotspots** — use `coverage-analysis`.
• **Are existing tests strong?** — use `test-gap-analysis` (mutation reasoning)

Skill page

Source