test-coverage

Evaluate unit test coverage for makeup-js modules and generate prioritized gap reports.

47|14|Updated Jan 8, 2020
One-click install
npx skills add https://github.com/makeup/makeup-js --skill test-coverage-makeup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/makeup/makeup-js/tree/main/.claude/skills/test-coverage
Command: npx skills add https://github.com/makeup/makeup-js --skill test-coverage-makeup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually auditing unit test coverage for individual makeup-js modules is time-consuming and often misses untested edge cases, uncovered branches, or gaps in negative test coverage. This skill automates the gap analysis process to help developers quickly identify where tests are missing.

Core Features & Use Cases

  • Scoped Coverage Analysis: Runs targeted coverage reports for a single specified module, avoiding noise from the entire monorepo.
  • Gap Identification: Manually cross-references source code and existing tests to flag uncovered branches, untested functions, edge cases, and missing negative test guards.
  • Prioritized Reporting: Outputs a concise, prioritized list of gaps ranked by impact, so developers can address the most critical missing tests first.
  • Use Case: A developer working on the makeup-roving-tabindex core module can use this skill to quickly discover that the branch handling disabled input elements has no test coverage, allowing them to add targeted tests without reviewing the entire codebase manually.

Quick Start

Use the test-coverage skill to evaluate unit test coverage for the makeup-modal module and get a prioritized list of untested code paths.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I find untested code paths in makeup-js modules?

To find untested code paths in makeup-js modules, you can run a scoped unit test coverage analysis that cross-references source code with existing tests to flag uncovered branches and missing negative test guards.

How do I audit unit test coverage for accessibility-focused JavaScript libraries?

Auditing unit test coverage for accessibility-focused JavaScript libraries involves evaluating individual modules to identify untested functions and edge cases, generating a prioritized gap report ranked by impact without modifying the source code.

What is the best way to identify missing negative test cases in headless UI components?

The best way to identify missing negative test cases in headless UI components is to perform a targeted gap analysis that cross-references source code against existing tests to prioritize uncovered branches and edge cases.

Can I run test coverage analysis on a single module in a monorepo without checking the whole codebase?

Yes, you can run scoped coverage analysis on a single specified module in a monorepo, which avoids noise from the entire codebase and outputs a prioritized list of gaps specific to that module's untested code paths.

Does the test coverage gap analysis write new tests or modify source code?

No, test coverage gap analysis does not write new tests or modify source code; it strictly evaluates existing unit test coverage to generate a prioritized report of uncovered branches, untested functions, and missing edge case tests.

Why does my makeup-js module have untested code paths for disabled input elements?

Untested code paths for disabled input elements occur when existing unit tests lack negative test guards for edge cases, which a targeted coverage gap analysis can identify and prioritize for manual review.