viamin/aidp

Overview

This skill is Test Analyzer, an expert in test-suite analysis, coverage assessment, and test quality evaluation. I examine existing tests to find coverage gaps, detect test smells, and produce prioritized, actionable recommendations that reduce risk and improve maintainability. Deliverables include a gap-focused coverage report, a catalog of test smells, and a pragmatic test strategy roadmap.

How this skill works

I inspect test code, run coverage tools (e.g., SimpleCov/Coverage.rb), and correlate coverage data with code complexity and business-critical paths. I statically analyze test structure and patterns to identify smells, brittle tests, and anti-patterns. I assess test reliability and performance by profiling slow or flaky tests and, where feasible, suggest mutation testing to validate test effectiveness. Findings are categorized by severity and mapped to concrete fixes.

When to use it

• Before a major refactor or release to ensure tests will catch regressions
• When CI shows slow or flaky tests that undermine developer confidence
• To prioritize test work by business and technical risk, not just coverage numbers
• When onboarding a new team or inheriting an unorganized test suite
• To evaluate testing strategy and rebalance the test pyramid (unit/integration/e2e)

Best practices

• Prioritize fixes by risk: address critical-path gaps first, then maintainability
• Mock only external boundaries; avoid mocking internals or private methods
• Write behavior-focused test descriptions and keep tests small and isolated
• Use coverage tools plus mutation testing to evaluate test effectiveness
• Keep test setup explicit; avoid hidden dependencies (mystery guests) and shared global state

Example use cases

• Generate a coverage gap analysis that highlights untested critical paths and edge cases
• Produce a test-smell catalog identifying fragile, slow, or over-mocked tests with file/line references
• Recommend a prioritized remediation plan: quick wins (flaky fixes), medium work (refactor helpers), long-term (introduce mutation testing)
• Assess test pyramid balance and suggest where to add unit, integration, or end-to-end tests
• Optimize suite performance by identifying slow tests and suggesting parallelization or improved mocking