test-discovery

Inventory tests, frameworks, coverage reports, and mappings in a project source tree.

Updated May 6, 2026
One-click install
npx skills add https://github.com/crgarcia12/compy --skill test-discovery-crgarcia12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-discovery
Source: https://github.com/crgarcia12/compy/tree/main/.github/skills/test-discovery
Command: npx skills add https://github.com/crgarcia12/compy --skill test-discovery-crgarcia12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a detailed inventory of test cases, frameworks, and coverage reports within a project, providing a factual overview without analysis or recommendations.

Core Features & Use Cases

  • Test Framework Detection: Identifies and records all test frameworks in use.
  • Test File Location: Locates and categorizes test files based on naming conventions and directory structure.
  • Test Case Counting: Counts individual test cases within each file.
  • Coverage Report Parsing: Extracts and documents coverage report data.
  • Test-to-Feature Mapping: Attempts to map test files to the source code they exercise.
  • Test Infrastructure Documentation: Records test utilities, fixtures, and CI integration details.

Quick Start

Run the test-discovery skill on your project directory to generate a comprehensive test inventory and analysis report.

Frequently Asked Questions about test-discovery

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

FAQPage Schema
How do I generate a test inventory and map test cases to source code?

To generate a test inventory, run the tool against your project directory to locate test files, count cases, detect frameworks, and map tests to the source code they exercise.

Can I parse coverage reports and detect multiple test frameworks in one project?

Yes, coverage report parsing and test framework detection are supported, extracting coverage data and identifying all test frameworks configured within the project source tree.

How does test-to-feature mapping work for locating and categorizing test files?

Test-to-feature mapping works by analyzing directory structures and naming conventions to locate test files, then attempting to map those files to the corresponding source code.

Does test infrastructure documentation require access to CI integration details?

Yes, generating test infrastructure documentation requires access to the project source tree and test framework configurations to record test utilities, fixtures, and CI integration details.

What is the best way to count individual test cases across different test frameworks?

The best way to count test cases is running an inventory script that scans test files, detects the active frameworks, and tallies individual test cases within each located file.