test: mutation hardening cycle — 79.91% to 84.77% (+4.86pp)#388
Conversation
…e.ts Mark Commander.js description and help text, console output formatting functions, and static fallback configuration as non-mutatable. These are pure presentation code with no behavioral impact -- mutating string literals in .description() or console.log formatting yields false survivors. execute.ts mutation score: 76.62% -> 93.02% (+16.4pp) Overall mutation score: 79.91% -> 83.40% (+3.49pp) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add tests asserting stageFlavor comma-join, artifactNames array content, listRecentArtifacts reverse sort order, and pipeline history entry fields. Extract history helper functions to outer describe scope for reuse. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add tests for bridge-run trailing newline, claude-native adapter name, comma-joined stageType, artifact names propagation, 0m elapsed default, stage-level observation counting, non-existent jsonl file handling, and prepareCycle backfill path when bet.runId is missing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…nId tracking Add test for nested directory creation with recursive mkdir in confidence calculator. Add tests verifying lastRunId tracks the most recent run by startedAt across multiple agent-attributed runs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add tests verifying predictionMatcher.match, calibrationDetector.detect, and frictionAnalyzer.analyze are invoked for each bet with a runId during cooldown. Add test for dojo diary writing and graceful skip when matchers are not injected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Strengthen the null-matcher guard test to verify that no logger.warn messages about prediction, calibration, or friction failures appear. This kills guard mutations that would remove the null check and let null reference errors be silently swallowed by the catch block. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR adds comprehensive test coverage for mutation testing across multiple feature modules, including Stryker configuration entries in gitignore and test-specific code comments. No production logic changes are introduced; focus is entirely on expanding test validation for existing functionality. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Approach
Remaining survivors (diminishing returns)
Test plan
npm run test:unit-- 3349 tests pass across 152 filesnpm run lint-- cleannpm run typecheck-- cleannpx stryker run-- 84.77% overall (above 70% break threshold)Generated with Claude Code
Summary by CodeRabbit
Tests
Chores