Description:
Mutation testing (#80, #214) is scored for settlement only. Run cargo mutants on the three satellite contracts, then close the surviving-mutant gaps with targeted tests until each crate reaches a mutation score of at least 85%.
Problem Statement & Context:
The satellites are now security-critical: the registry holds bonds and the proof registry is the root of trust. A high line-coverage number can hide tests that assert nothing.
Scope & Acceptance Criteria:
- A baseline report for each crate.
- New tests that kill the surviving mutants, and a documented justification for any equivalent mutants.
- A score of at least 85% per crate, recorded in
docs/.
- Out of scope: settlement.
Implementation Guidelines:
- Key Files/Modules: each satellite
src/test.rs, docs/.
- Design/Architecture: Prioritize mutants in auth checks, comparisons, and arithmetic.
- Edge Cases/Constraints: A long runtime (shard with
--shard).
- Testing: As described in the scope.
Definition of "Done":
- Scores documented, and tests merged.
- Reviewed and approved.
Resources:
Complexity: High (200 points)
Description:
Mutation testing (#80, #214) is scored for settlement only. Run
cargo mutantson the three satellite contracts, then close the surviving-mutant gaps with targeted tests until each crate reaches a mutation score of at least 85%.Problem Statement & Context:
The satellites are now security-critical: the registry holds bonds and the proof registry is the root of trust. A high line-coverage number can hide tests that assert nothing.
Scope & Acceptance Criteria:
docs/.Implementation Guidelines:
src/test.rs,docs/.--shard).Definition of "Done":
Resources:
Complexity: High (200 points)