testing

Validate test coverage and add minimal edge-case tests for task files.

31|3|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/dhruvbaldawa/ccconfigs --skill testing-dhruvbaldawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/dhruvbaldawa/ccconfigs/tree/main/experimental/skills/testing
Command: npx skills add https://github.com/dhruvbaldawa/ccconfigs --skill testing-dhruvbaldawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates test coverage and quality by focusing on behavior validation, identifying gaps in tests, and ensuring statements coverage above 80%. It is intended for task files located in the testing/ directory that require automated validation before status updates. It also adds minimal tests for genuinely missing edge cases.

Core Features & Use Cases

  • Behavior-focused validation: assesses existing tests for coverage of expected behaviors.
  • Gap detection: identifies empty or null inputs, boundary cases, race conditions, and potential errors.
  • Minimal test augmentation: adds targeted tests only where edge cases are genuinely missing.
  • Coverage enforcement: ensures statement coverage >80% and branches >75% before marking readiness.

Quick Start

Use the testing workflow to validate the task file under testing/ and update status to READY_FOR_REVIEW when criteria are met.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce minimum code coverage thresholds for unit tests?

Behavior-focused test validation assesses existing unit tests to verify they cover expected behaviors, then identifies missing edge cases like null inputs and boundary conditions to ensure comprehensive quality assurance.

How do I automatically detect missing edge cases in my test suite?

Edge-case gap detection automatically analyzes existing tests to identify missing boundary conditions, empty inputs, race conditions, and potential errors, adding minimal targeted tests only where genuinely needed.

What is the best way to validate test coverage before marking a task as ready?

The best way to validate test coverage is using an automated workflow that evaluates task files in the testing directory, enforcing behavior validation and coverage thresholds before updating the task status to READY_FOR_REVIEW.

Does test coverage validation work with task files in a specific directory?

Yes, test coverage validation applies specifically to task files located in the testing/ directory across projects, analyzing existing tests and augmenting them with minimal edge-case tests where gaps are found.

When should I not use automated test augmentation for edge cases?

Automated test augmentation should not be used as a complete replacement for manual test design, as it only adds targeted tests for genuinely missing edge cases rather than building comprehensive behavior validation from scratch.