Analyze test coverage and identify modules needing tests.
Steps
Run all tests and collect results
cargo test 2>&1
Note total test count and any failures.
Identify modules without tests
Search for Rust source files and check for #[cfg(test)] blocks:
# Find files without test modules
for f in src/**/*.rs; do
if ! grep -q '#\[cfg(test)\]' "$f" 2>/dev/null; then
echo "$f"
fi
done
Analyze untested modules
For each untested module, identify:
Public functions that should have unit tests
Complex logic that would benefit from testing
Edge cases in the implementation
Generate coverage report
Report modules by priority:
Critical: Core logic (session management, state transitions)
High: Input handling, navigation logic
Medium: Utility functions, helpers
Low: Simple structs, trivial implementations
Coverage Categories
Modules that SHOULD have tests
State management (app/state.rs, session/mod.rs)
Business logic (filters, calculations, validations)
Type conversions and parsing
Navigation and routing logic
Modules that MAY skip tests
Pure TUI rendering (requires integration testing)
PTY interaction (requires real terminal)
Simple re-exports and type aliases
Example Report
Test Coverage Report:
Total tests: 261
Modules with tests: 26/42 (62%)
High Priority Gaps:
- src/input/dispatcher.rs - No direct tests (routes to handlers)
- src/input/session_mode.rs - No tests (PTY interaction)
Medium Priority Gaps:
- src/tui/views/*.rs - Rendering modules (integration tests recommended)
Coverage by Area:
- Core (app, session, hooks): 80%
- Input handling: 40%
- TUI rendering: 20%
- Utilities: 90%
Suggestions
After running this skill, consider:
Adding unit tests to high-priority gaps
Creating integration test scaffolding for TUI tests
Adding property-based tests for parsing/filtering logic
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: ivan-brko-panoptes-test-coverage3description: Test Coverage Skill4---56# Test Coverage Skill78Analyze test coverage and identify modules needing tests.910## Steps11121. **Run all tests and collect results**13 ```bash14 cargo test 2>&115 ```16 Note total test count and any failures.17182. **Identify modules without tests**19 Search for Rust source files and check for `#[cfg(test)]` blocks:20 ```bash21 # Find files without test modules22 for f in src/**/*.rs; do23 if ! grep -q '#\[cfg(test)\]' "$f" 2>/dev/null; then24 echo "$f"25 fi26 done27 ```28293. **Analyze untested modules**30 For each untested module, identify:31 - Public functions that should have unit tests32 - Complex logic that would benefit from testing33 - Edge cases in the implementation34354. **Generate coverage report**36 Report modules by priority:37 - **Critical**: Core logic (session management, state transitions)38 - **High**: Input handling, navigation logic39 - **Medium**: Utility functions, helpers40 - **Low**: Simple structs, trivial implementations4142## Coverage Categories4344### Modules that SHOULD have tests45- State management (`app/state.rs`, `session/mod.rs`)46- Business logic (filters, calculations, validations)47- Type conversions and parsing48- Navigation and routing logic4950### Modules that MAY skip tests51- Pure TUI rendering (requires integration testing)52- PTY interaction (requires real terminal)53- Simple re-exports and type aliases5455## Example Report5657```58Test Coverage Report:5960Total tests: 26161Modules with tests: 26/42 (62%)6263High Priority Gaps:64- src/input/dispatcher.rs - No direct tests (routes to handlers)65- src/input/session_mode.rs - No tests (PTY interaction)6667Medium Priority Gaps:68- src/tui/views/*.rs - Rendering modules (integration tests recommended)6970Coverage by Area:71- Core (app, session, hooks): 80%72- Input handling: 40%73- TUI rendering: 20%74- Utilities: 90%75```7677## Suggestions7879After running this skill, consider:801. Adding unit tests to high-priority gaps812. Creating integration test scaffolding for TUI tests823. Adding property-based tests for parsing/filtering logic8384---85> Converted and distributed by [TomeVault](https://tomevault.io/claim/ivan-brko) — claim your Tome and manage your conversions.86<!-- tomevault:4.0:skill_md:2026-04-13 -->
Run npx skillmds@latest add tomevault-io/ivan-brko-panoptes-test-coverage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Test Coverage Skill It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.