behavioral-mutation-analyzer
SolidAnalyzes 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.
Install
Quality Score: 87/100
Skill Content
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
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.
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.
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.