sumo-qa-strengthening-tests

Triage mutation-testing survivors and draft one strengthening test per real mutant.

5|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-strengthening-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sumo-qa-strengthening-tests
Source: https://github.com/sumithr/sumo-qa/tree/main/skills/sumo-qa-strengthening-tests
Command: npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-strengthening-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you eliminate weak assertions and mutation-testing survivors by guiding you to strengthen only the tests—without changing production code.

Core Features & Use Cases

  • Mutation-survivor triage with confirmation gates: Separates likely equivalent/tautological mutants from likely real behavior gaps before writing any changes.
  • Single-mutant walk-through: Processes survivors one at a time, asking the user to confirm whether each mutant is truly equivalent in practice.
  • Technique-driven strengthening: Selects exactly one ISTQB-grounded technique per real mutant and uses it to draft a targeted strengthening test.
  • Hard safety gate for production code: Explicitly prevents production edits; survivors found due to wrong production behavior must be handled by a different workflow.

Quick Start

Ask your AI coding assistant to run mutation test follow-up using sumo-qa-strengthening-tests for your mutation report on the target module, and confirm each survivor as equivalent or real before it writes strengthening tests.

Frequently Asked Questions about sumo-qa-strengthening-tests

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

FAQPage Schema
How do I kill surviving mutants from Pitest or Stryker without changing production code?

To kill surviving mutants without changing production code, triage each survivor to distinguish equivalent mutants from real behavior gaps, then add exactly one catalogue technique-driven strengthening test per real mutation survivor.

What is the best way to handle equivalent mutants in mutation testing?

Handling equivalent mutants requires walking each survivor through an equivalence and tautology triage process with confirmation gates, then suppressing confirmed equivalents via tooling annotations or configuration.

How do I strengthen weak assertions in pytest using boundary value analysis?

Strengthen weak assertions by applying ISTQB-grounded techniques like boundary value analysis to draft exactly one targeted strengthening test per real mutation survivor while keeping production code unchanged.

Does this mutation testing approach work when a survivor indicates wrong production behavior?

No, this approach explicitly prevents production edits. Surviving mutants found due to wrong production behavior must be handled by a different workflow, as this process strictly strengthens only tests.

Can I use mutation testing tools like mutmut to improve assertion quality in TDD?

Yes, you can use mutation testing reports from mutmut to improve assertion quality by processing survivors one at a time, confirming each as equivalent or real, and drafting targeted strengthening tests for the TDD red phase.