Loopgate should make agents write tests that challenge behavior, not just chase 100% line coverage.
[ ] - Use the Mutmut-generated json to go mutant hunting
[ ] - Strengthen the tests deterministically
[X ] - Create a concise docs/example page showing how to add mutation testing to a Ralph-managed Python project.
Suggested scope:
[X ]- use mutmut as the first Python example
[X ]- show modern config names such as source_paths instead of deprecated settings
[X ]- show the import-path gotcha for projects that use src/ or package modules
[X ]- explain how to interpret surviving mutants
[X ]- keep it practical: commands, expected output shape, common failure modes
Acceptance criteria:
[X ]- a new user can copy the config and run the command
[X ]- docs explain why mutation testing catches weak agent-written tests
[X ]- no broad framework comparison; keep the page short and actionable
Loopgate should make agents write tests that challenge behavior, not just chase 100% line coverage.
[ ] - Use the Mutmut-generated json to go mutant hunting
[ ] - Strengthen the tests deterministically
[X ] - Create a concise docs/example page showing how to add mutation testing to a Ralph-managed Python project.
Suggested scope:
[X ]- use
mutmutas the first Python example[X ]- show modern config names such as
source_pathsinstead of deprecated settings[X ]- show the import-path gotcha for projects that use
src/or package modules[X ]- explain how to interpret surviving mutants
[X ]- keep it practical: commands, expected output shape, common failure modes
Acceptance criteria:
[X ]- a new user can copy the config and run the command
[X ]- docs explain why mutation testing catches weak agent-written tests
[X ]- no broad framework comparison; keep the page short and actionable