mutation-analyzer

Analyze Infection mutation testing logs to generate a prioritized Markdown remediation plan.

9|Updated Apr 12, 2020

Search Tags:#code-quality #test-automation #mutation-testing #software-testing #infection #mutation-analysis

Ready to run

npx skills add https://github.com/Wtyd/githooks --skill mutation-analyzer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mutation-analyzer
Source: https://github.com/Wtyd/githooks/tree/main/.claude/skills/mutation-analyzer
Command: npx skills add https://github.com/Wtyd/githooks --skill mutation-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analiza informes de Infection para convertir una lista bruta de mutants escapados en un plan de refuerzo de tests priorizado, ayudando a endurecer el código y reducir riesgos de producción.

Core Features & Use Cases

Análisis centralizado de logs de Infection (infection-summary.log, per-mutator.md, infection.log) para identificar patrones y guiar mejoras de calidad.
Clasificación de mutants en categorías (ALTA, MEDIA, EQUIVALENTE, COSMÉTICO, AMBIGUO) con evidencia citada de tests o código, para priorizar acciones.
Generación de un informe estructurado en Markdown con prioridades, candidatos a correcciones de código y plan de acción orientado a ROI.

Quick Start

Proporcione los archivos de Infection y solicite un plan de remediación priorizado.

Frequently Asked Questions about mutation-analyzer

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

FAQPage Schema

How do I analyze Infection mutation testing logs to prioritize test hardening?▼

Mutation testing analysis parses Infection logs like infection-summary.log and per-mutator.md to classify escaped mutants into HIGH, MEDIUM, and AMBIGUOUS priorities. This generates a structured Markdown remediation plan with actionable code changes and cited test evidence.

What is the best way to classify escaped mutants from a mutation testing report?▼

Classifying escaped mutants involves categorizing them into HIGH, MEDIUM, EQUIVALENT, COSMETIC, and AMBIGUOUS groups based on Infection log evidence. This prioritization guides test hardening actions by focusing on high-risk code paths and targeted fixes.

How do I generate a remediation plan from infection.log and infection-summary.log?▼

Generating a remediation plan from infection logs involves analyzing mutation testing outputs to identify patterns and produce a centralized Markdown report. The report details prioritized fixes, recommended next steps, and code change candidates oriented towards ROI.

Does mutation analysis require specific Infection output files to prioritize test fixes?▼

Mutation analysis relies on specific Infection output files, including infection-summary.log, per-mutator.md, and infection.log. Providing these logs enables the identification of escaped mutants and the generation of a structured, prioritized remediation plan.

Why should I categorize mutation testing results into HIGH, MEDIUM, and AMBIGUOUS items?▼

Categorizing mutation testing results into HIGH, MEDIUM, and AMBIGUOUS items helps prioritize test hardening by focusing on critical escaped mutants first. This classification uses cited evidence from tests or code paths to guide targeted fixes and reduce production risks.

What limitations exist when using mutation analysis logs to harden tests?▼

Mutation analysis limitations involve handling EQUIVALENT, COSMETIC, and AMBIGUOUS mutants which may not require test fixes. The process focuses on generating actionable remediation plans for HIGH and MEDIUM items while carefully evaluating ambiguous mutation evidence.