test: enforce full VFBuilders coverage and fix construction regressions - #25
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 (22)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds test dependencies, JaCoCo coverage checks, CI coverage-report uploads, and tests across plugin subsystems. It also updates station placement checks, display handling, inventory lore handling, and configuration resources. ChangesTest coverage and station behavior
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~30 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The change adds tests, a coverage gate, and small station-behavior safeguards. No concrete merge-blocking issue was found, so it is ready to merge after the normal CI run. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The inspected changes strengthen placement safeguards and preserve construction vetoes before materials are consumed. A new plugin-directed retry option and incomplete integration coverage warrant caution. Existing event-ordering and station-cleanup limitations remain, but the inspected comparison does not establish that this PR materially worsens them. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 6.06% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 66 functions across 16 files. (6 skipped: 6 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
A rabbit checks the coverage trail Comment |
VFBuilders had no executable test coverage. Add regression tests for construction state and material accounting, menus/permissions, placement timers, chunk events/displays, configuration, persistence and lifecycle.
Fix the failures exposed by those tests:
Maven verify now enforces 100% production line, branch and instruction coverage without exclusions; CI uploads reports. Remove only redundant private checks already guaranteed by caller/API contracts. Checksum-pinned ModelEngine/NBTAPI test inputs and a provided CoreProtect API make VehicleFramework boundary mocks load correctly; these are not bundled.
Validation: Java 21 clean offline Maven verify passes 32 tests, zero failures/errors/skips; 904/904 lines, 408/408 branches, 3,829/3,829 instructions. Regression tests were observed failing before fixes. External server/plugin boundaries are mocked; no live deployment performed.
Summary by CodeRabbit