ce-test-pruning-expert

Name: ce-test-pruning-expert
Availability: InStock
Author: moffran

Identify redundant tests using unique-line counts and overlap fingerprints.

78|15|Updated May 1, 2023

Search Tags:#risk-management #evidence-based #test-coverage #qa-automation #test-pruning #redundant-tests

Ready to run

npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-pruning-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-test-pruning-expert
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-test-pruning-expert
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-pruning-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prune test suites by identifying redundant or low-value tests using unique-line counts and overlap fingerprints while preserving behavioral coverage, aligning with ADR-030 guidelines.

Core Features & Use Cases

Evidence-based pruning identifies zero-unique-line tests as candidates and evaluates overlap fingerprints to reduce duplication.
Supports multiple workflow options (A: Test-Focused, B: Code-Focused, C: Full Cycle) with safety gates to preserve behavior.
Generates artifacts such as reports/over_testing/per_test_summary.csv and reports/over_testing/redundant_tests.csv for review and action.
Useful when triaging test reports, consolidating near-duplicate tests, and guiding safe removals.

Quick Start

Select an option (A, B, or C) and run the full pruning workflow, then review the generated reports to act on candidate removals.

Frequently Asked Questions about ce-test-pruning-expert

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

FAQPage Schema

How do I identify redundant tests without losing behavioral coverage?▼

Test pruning identifies redundant tests by comparing unique line counts and overlap fingerprints to ensure behavioral coverage is preserved. Zero-unique-line tests are flagged as removal candidates while safety gates validate the changes.

What is evidence-based test pruning and how does it work?▼

Evidence-based test pruning evaluates test suites by analyzing unique lines and overlap fingerprints to detect duplication. It generates per-test summaries and redundant test lists to guide safe, documented removals.

How do I run a test pruning workflow across different focus scenarios?▼

You can run the test pruning workflow using Option A for test-focused analysis, Option B for code-focused analysis, or Option C for a full cycle. Each generates reports in the over_testing directory to review candidate removals.

Can I automate QA test consolidation for near-duplicate test suites?▼

Yes, QA automation test consolidation triages near-duplicate tests by evaluating overlap fingerprints. The workflow outputs redundant_tests.csv and per_test_summary.csv artifacts to guide safe test removals.

What safety checks are included when removing low-value tests?▼

Safety checks validate removals and document risk notes to ensure behavioral coverage is preserved during test pruning. These gates align with ADR-030 guidelines to prevent unintended coverage loss.

What reports are generated to document redundant test removals?▼

The test pruning process generates per_test_summary.csv and redundant_tests.csv in the reports/over_testing directory. These artifacts provide per-test line counts and candidate lists for review and action.