behavioral-mutation-analyzer

Solid

Analyzes surviving mutants from mutation testing to identify why tests failed to detect them. Takes repository code, test suite, and mutation testing results as input. Identifies root causes including insufficient coverage, equivalent mutants, weak assertions, and missed edge cases. Automatically generates actionable test improvements and new test cases. Use when analyzing mutation testing results, improving test suite effectiveness, investigating low mutation scores, generating tests to kill surviving mutants, or enhancing test quality based on mutation analysis.

Testing & QA 160 stars 17 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Behavioral Mutation Analyzer ## Overview This skill systematically analyzes surviving mutants from mutation testing to understand test suite weaknesses and automatically generate improvements. It identifies why mutants survived, categorizes root causes, and produces actionable test enhancements to increase mutation detection rates. ## Analysis Workflow ### Step 1: Input Collection and Validation Gather required inputs and verify completeness: **Required Inputs:** - Repository source code (path or files) - Test suite (test files and framework) - Mutation testing results (report file or data) **Mutation Result Formats:** - PIT (Java): XML or HTML reports - Stryker (JavaScript/TypeScript): JSON reports - mutmut (Python): result files - Pitest, Infection (PHP), Cosmic Ray, etc. **Validation checklist:** - [ ] Source code accessible - [ ] Test suite runnable - [ ] Mutation results parseable - [ ] Mutation tool and version identified ### Step 2: Surviving Mutant Extraction Parse mutation results to identify all surviving mutants: **Extract for each mutant:** - Mutant ID - Source file and line number - Mutation operator (e.g., boundary change, negation) - Original code - Mutated code - Status (survived/killed/timeout/error) **Focus on survived mutants:** Filter out killed mutants and focus analysis on survivors that indicate test weaknesses. ### Step 3: Root Cause Classification Analyze each surviving mutant to determine why it survived: #### Category 1: Insufficien...

Details

Author
ArabelaTso
Repository
ArabelaTso/Skills-4-SE
Created
6 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

mutants

This skill should be used when the question is whether a test suite is actually any good — when the user says "are these tests any good", "what am I not testing", "coverage is 100% but I still shipped a bug", "improve the tests for this", "is this well tested", "find gaps in my tests", "mutation testing", or asks for tests to be written for existing code and the useful ones need identifying. Measures which bugs the suite would actually catch by mutating the source, then triages the survivors into real gaps and equivalent mutants.

1 Updated 3 weeks ago
lkc-studio
Testing & QA Listed

mutants

This skill should be used when the question is whether a test suite is actually any good — when the user says "are these tests any good", "what am I not testing", "coverage is 100% but I still shipped a bug", "improve the tests for this", "is this well tested", "find gaps in my tests", "mutation testing", or asks for tests to be written for existing code and the useful ones need identifying. Measures which bugs the suite would actually catch by mutating the source, then triages the survivors into real gaps and equivalent mutants.

1 Updated 3 weeks ago
lkc-studio
Testing & QA Listed

mutation-testing

When the user wants to measure or improve the *quality* of their existing test suite via mutation testing. Use when the user mentions "mutation testing," "mutation score," "Stryker," "PIT," "PITest," "mutmut," "go-mutesting," "Mutmut," "mutator," "killed mutant," "surviving mutant," "mutation coverage," or "is our coverage strong." For line coverage see code-coverage. For overall strategy see test-strategy.

2 Updated 1 weeks ago
aks-builds