AI coding

Mutation testing and test strength

• Assertions That Resist Weakening: A Pattern Library
• How to Spot a Test That Passes for the Wrong Reason
• Mutation Testing on a Budget: Picking the Lines to Kill
• Trimming Mutation Scope: Files, Operators and Lines
• When an Agent Writes the Mutant: Prompt and Sandbox
• A Mutation Score That Won't Mislead: Choosing the Denominator
• Assertion Density per Changed Line: Setting a Floor and Measuring
• Assertions That Survive a Mutant: A Pattern Library
• Equivalence or a Real Bug: A Triage Worksheet for Survivors
• Killing Mutants the Cheap Way: Schemata and Coverage Seeding
• Parallelising a Mutation Run: Sharding and Retry Cost
• Read-Only Contract for the Test Runner: Paths, Env, Exit Codes
• Reading a Coverage Report for Lines That Prove Nothing
• Seeding Bugs to Calibrate a Mutation Gate: Count and Placement
• Seeding Mutation Runs from Coverage and Recent Diffs
• When a Mutant Survives: Triage, Equivalence and Real Bugs
• Writing Assertions a Mutant Cannot Survive: A Pattern Library
• Writing Test Oracles an Agent Cannot Fake