test-analyzer

Analyze test suites for missing behavioral scenarios and test smells.

4|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/euxx/claude-skills-for-copilot --skill test-analyzer-euxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-analyzer
Source: https://github.com/euxx/claude-skills-for-copilot/tree/main/skills/test-analyzer
Command: npx skills add https://github.com/euxx/claude-skills-for-copilot --skill test-analyzer-euxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you judge whether tests actually protect behavior, not just lines of code, so missing scenarios are caught before regressions ship.

Core Features & Use Cases

  • Critical gap detection: Finds untested error paths, boundary cases, state transitions, core business logic, and security-sensitive inputs.
  • Test quality assessment: Evaluates resilience, descriptiveness, isolation, completeness, and setup clarity using DAMP principles.
  • Test smell detection: Flags over-mocking, implementation-detail assertions, tests with no assertions, time dependence, and ordering assumptions.
  • Use case: Review a recently added test suite after a refactor to identify which user-visible behaviors still need coverage and which tests should be rewritten for higher value.

Quick Start

Ask the test analyzer skill to review the tests for the specified file, folder, or suite and report missing behavioral scenarios and brittle test patterns.

Frequently Asked Questions about test-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find missing behavioral scenarios in my test suite after refactoring code?

Test coverage analysis identifies missing behavioral scenarios by evaluating error handling paths, boundary cases, state transitions, and security-sensitive inputs. It applies DAMP principles to detect coverage gaps and priority-ranked remediation guidance after code refactoring.

What are test smells and how do I detect over-mocking in my unit tests?

Test smells include over-mocking, implementation-detail assertions, tests with no assertions, time dependence, and ordering assumptions. Test quality assessment flags these brittle patterns by evaluating resilience, descriptiveness, isolation, and setup clarity using DAMP principles.

How do I assess test quality using DAMP principles for an existing project?

DAMP principles assess test quality by evaluating resilience, descriptiveness, isolation, completeness, and setup clarity. Analyzing test suites against these criteria identifies brittle test patterns and generates priority-ranked remediation guidance for coverage gaps.

Can I analyze test coverage quality for a specific folder or file instead of a full suite?

Test coverage quality analysis applies to individual files, specific folders, or full test suites. It evaluates missing behavioral scenarios and test smells across the selected scope, providing priority-ranked remediation guidance for identified coverage gaps.

What is the best way to identify untested error paths and boundary cases in my tests?

Critical gap detection finds untested error paths, boundary cases, state transitions, core business logic, and security-sensitive inputs. Analyzing test coverage quality highlights these missing behavioral scenarios and generates remediation guidance to prevent regressions.

Why does my test suite have coverage gaps even though line coverage is high?

High line coverage often misses behavioral scenarios like error handling, state transitions, and security-sensitive inputs. Test coverage analysis evaluates test quality beyond lines of code, detecting coverage gaps and implementation-detail assertions that fail to protect actual behavior.