Skip to main content Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill mutation-testingLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
Métiers associés SOC
Basé sur la classification professionnelle SOC
Explorateur de fichiers
8 fichiers name mutation-testing description Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate. Use when evaluating test quality, identifying weak tests, or proving tests actually catch bugs. category specialized-testing priority high tokenEstimate 900 agents ["qe-test-generator","qe-coverage-analyzer","qe-quality-analyzer","qe-mutation-tester"] implementation_status optimized optimization_version 1 last_optimized "2025-12-02T00:00:00.000Z" dependencies [] quick_reference_card true tags ["mutation","stryker","test-quality","kill-rate","assertions","effectiveness"] trust_tier 3 validation {"schema_path":"schemas/output.json","validator_path":"scripts/validate-config.json","eval_path":"evals/mutation-testing.yaml"}
Mutation Testing
<default_to_action>
When validating test quality or improving test effectiveness:
MUTATE code (change + to -, >= to >, remove statements)
RUN tests against each mutant
VERIFY tests catch mutations (kill mutants)
IDENTIFY surviving mutants (tests need improvement)
STRENGTHEN tests to kill surviving mutants
Quick Mutation Metrics:
Mutation Score = Killed / (Killed + Survived)
Target: > 80% mutation score
Surviving mutants = weak tests
Critical Success Factors:
High coverage ≠ good tests (100% coverage, 0% assertions)
Mutation testing proves tests actually catch bugs
Focus on critical code paths first
</default_to_action>
Quick Reference Card
When to Use
Evaluating test suite quality
Finding gaps in test assertions
Proving tests catch bugs
Before critical releases
Mutation Score Interpretation
Score Interpretation 90%+ Excellent test quality 80-90% Good, minor improvements 60-80% Needs attention < 60% Significant gaps
Common Mutation Operators
Category Original Mutant Arithmetic a + ba - bRelational x >= 18x > 18Logical a && ba || bConditional if (x)if (true)Statement return x(removed)
How Mutation Testing Works
function isAdult (age ) {
return age >= 18 ;
}
test ('18 is adult' , () => {
expect (isAdult (18 )).toBe (true );
});
test ('19 is adult' , () => {
expect (isAdult (19 )).toBe (true );
});
Using Stryker
npm install --save-dev @stryker-mutator/core @stryker-mutator/jest-runner
npx stryker init
{
"packageManager" : "npm" ,
"reporters" : [ "html" , "clear-text" , "progress" ] ,
"testRunner" : "jest" ,
"coverageAnalysis" : "perTest" ,
"mutate" : [
"src/**/*.ts" ,
"!src/**/*.spec.ts"
] ,
"thresholds" : {
"high" : 90 ,
"low" : 70 ,
"break" : 60
}
}
Mutation Score: 87.3%
Killed: 124
Survived: 18
No Coverage: 3
Timeout: 1
Fixing Surviving Mutants
function calculateDiscount (quantity ) {
if (quantity >= 10 ) {
return 0.1 ;
}
return 0 ;
}
test ('large order gets discount' , () => {
expect (calculateDiscount (15 )).toBe (0.1 );
});
test ('exactly 10 gets discount' , () => {
expect (calculateDiscount (10 )).toBe (0.1 );
});
test ('9 does not get discount' , () => {
expect (calculateDiscount (9 )).toBe (0 );
});
Agent-Driven Mutation Testing
await Task ("Mutation Analysis" , {
targetFile : 'src/payment.ts' ,
generateMissingTests : true ,
minScore : 80
}, "qe-test-generator" );
await Task ("Coverage Quality Analysis" , {
coverageData : coverageReport,
mutationData : mutationReport,
identifyWeakCoverage : true
}, "qe-coverage-analyzer" );
Agent Coordination Hints
Memory Namespace aqe/mutation-testing/
├── mutation-results/* - Stryker reports
├── surviving/* - Surviving mutants
├── generated-tests/* - Tests to kill mutants
└── trends/* - Mutation score over time
Fleet Coordination const mutationFleet = await FleetManager .coordinate ({
strategy : 'mutation-testing' ,
agents : [
'qe-test-generator' ,
'qe-coverage-analyzer' ,
'qe-quality-analyzer'
],
topology : 'sequential'
});
Related Skills
Remember High code coverage ≠ good tests. 100% coverage but weak assertions = useless. Mutation testing proves tests actually catch bugs.
Focus on critical paths first. Don't mutation test everything - prioritize payment, authentication, data integrity code.
With Agents: Agents run mutation analysis, identify surviving mutants, and generate missing test cases to kill them. Automated improvement of test quality.
Run History After each mutation test run, append results to run-history.json in this skill directory:
node -e "
const fs = require('fs');
const h = JSON.parse(fs.readFileSync('.claude/skills/mutation-testing/run-history.json'));
h.runs.push({date: new Date().toISOString().split('T')[0], mutation_score_pct: SCORE, killed: KILLED, survived: SURVIVED});
fs.writeFileSync('.claude/skills/mutation-testing/run-history.json', JSON.stringify(h, null, 2));
"
Read run-history.json before each run to track score improvements over time.
Skill Composition
Before mutation testing → Run /qe-test-generation to ensure tests existAfter mutation results → Use /qe-coverage-analysis to prioritize improvement areasQuality gate → Feed results into /qe-quality-assessment for ship/no-ship decision
Gotchas
Stryker requires --testRunner jest explicitly if both jest and vitest are installed
Mutating >= to > in date comparisons rarely gets killed — add boundary tests
Running on files >500 LOC will timeout; use --mutate to target specific functions
--concurrency defaults to CPU count which OOMs in containers — set to 2 