test: reach 100% runtime line coverage and fix surgery bugs - #24
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (14)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe pull request configures Maven tests and JaCoCo coverage reporting, adds tests for surgery lifecycle and mechanics, and changes surgery item handling and duration arithmetic. ChangesTest and coverage pipeline
Surgery item handling
Duration arithmetic
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The surgery fixes and coverage configuration have no identified issue that needs resolution before merging. Complete the normal build checks before merge.
Comment |
Surgery starts at 64/1,133 covered executable lines (5.65%). Add behavioral tests for player consent, operation state, all tools and complications, success/failure handling, menus, configuration, events and plugin lifecycle. The suite now covers all 1,139 production lines with no exclusions; Maven enforces zero missed lines and CI uploads JaCoCo reports.
The tests reproduced three bugs, fixed here with their regressions:
Validation: Java 21
mvn clean verify; 98 tests passed, no failures or skips. Runtime JAR filename/version check passed. JaCoCo: lines 1,139/1,139 (100%), instructions 6,028/6,031, branches 631/649. The enforced metric is executable-line coverage across all runtime classes; maintenance/build scripts are outside the ranking.Bug fixes and coverage changes stay together in this PR, including CodeRabbit follow-ups.