test-suite-curation

Audit regression test suites to identify redundant and low-value tests.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill test-suite-curation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-suite-curation
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/test-suite-curation
Command: npx skills add https://github.com/rabbicse/go-projects --skill test-suite-curation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams safely reduce and reorganize large regression suites without losing meaningful coverage, by replacing intuition-based cleanup with evidence-based test analysis.

Core Features & Use Cases

  • Coverage fingerprinting: Identifies exactly which lines and branches each test covers so you can see unique coverage and overlap.
  • Duplicate and redundancy analysis: Clusters near-identical tests, compares execution profiles, and separates true redundancy from tests that only look similar.
  • History-driven pruning and tiering: Mines CI results for never-failing or flaky tests, then helps classify tests into smoke, core, and extended tiers based on risk and defect-catch history.
  • Safe removal workflow: Requires quarantine, human approval, observation windows, and a per-test audit log before any deletion is finalized.

Quick Start

Ask the assistant to audit your regression suite, find redundant or low-value tests, and produce a quarantine-first curation plan with an auditable deletion record.

Frequently Asked Questions about test-suite-curation

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

FAQPage Schema
How do I find redundant tests in a regression test suite?

Test suite curation identifies low-value tests by mining CI history for never-failing or flaky tests and applying mutation confirmation to verify defect-catch effectiveness. This replaces intuition-based cleanup with evidence-based retention decisions.

What is the best way to safely remove obsolete tests without losing coverage?

Test tiering classifies tests into smoke, core, and extended tiers by mining CI history for flaky or never-failing tests and evaluating defect-catch history. This history-driven pruning restructures execution based on risk and value.

Do I need per-test coverage fingerprints to restructure my test tiers?

Mutation testing confirms test suite value by verifying that specific tests actually catch injected defects during curation. This mutation confirmation validates whether tests flagged as redundant or low-value are truly safe to quarantine and delete.

When should I not use automated test suite pruning?

Duplicate detection in a test suite works by clustering near-identical tests using AST similarity and comparing execution profiles. This coverage fingerprinting distinguishes true redundancy from tests that only look similar but provide unique branch coverage.